From: "Ulrich Weigand" <uweigand@de.ibm.com>
To: brobecker@adacore.com (Joel Brobecker)
Cc: palves@redhat.com (Pedro Alves), gdb-patches@sourceware.org
Subject: [rfc v4][0/6] Remote /proc file access (Re: [rfc v3][0/6] Remote /proc file access)
Date: Thu, 19 Jan 2012 10:01:00 -0000 [thread overview]
Message-ID: <201201191000.q0JA04Bu008569@d06av02.portsmouth.uk.ibm.com> (raw)
In-Reply-To: <20120119063034.GF31383@adacore.com> from "Joel Brobecker" at Jan 19, 2012 10:30:34 AM
Joel Brobecker wrote:
> > Joel, could you try one (hopefully) last time, using the patch below instead
> > of the original 5/6 patch? Thanks again!
>
> Apparently, patch 6 failed to apply on top of patch 5. Or maybe
> I didn't apply patch 5 correctly. It's a little too large for me
> to figure it out at a glance. Can you resend me the whole series
> the same way you sent it the first time. It was extremely convenient,
> because all I had to do was save your email in an mbox, and then
> use "git am" to apply them. That way, I know I'm applying them
> correctly.
Oops, sorry for the extra difficulties ... I'll be re-sending
the whole patch series, rebased on current CVS head.
There should be no other changes except those discussed on the list.
Thanks,
Ulrich
--
Dr. Ulrich Weigand
GNU Toolchain for Linux on System z and Cell BE
Ulrich.Weigand@de.ibm.com
next prev parent reply other threads:[~2012-01-19 10:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-17 19:41 [rfc v3][0/6] Remote /proc file access Ulrich Weigand
2012-01-17 20:19 ` Pedro Alves
2012-01-17 20:33 ` Ulrich Weigand
2012-01-18 11:46 ` Joel Brobecker
2012-01-18 12:09 ` Pedro Alves
2012-01-18 15:33 ` Ulrich Weigand
2012-01-19 10:00 ` Joel Brobecker
2012-01-19 10:01 ` Ulrich Weigand [this message]
2012-01-19 16:03 ` [rfc v4][0/6] Remote /proc file access (Re: [rfc v3][0/6] Remote /proc file access) Joel Brobecker
2012-01-20 10:01 ` Joel Brobecker
2012-01-20 10:02 ` Ulrich Weigand
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201201191000.q0JA04Bu008569@d06av02.portsmouth.uk.ibm.com \
--to=uweigand@de.ibm.com \
--cc=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=palves@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox