public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: "H.J. Lu" <hjl.tools@gmail.com>
Cc: Binutils Development <binutils@sourceware.org>,
	       GDB Patches <gdb-patches@sourceware.org>,
	       Pedro Alves <palves@redhat.com>
Subject: Re: [PATCH/RFC 01/02 v2] Refactor PRPSINFO handling on Binutils
Date: Mon, 17 Dec 2012 17:51:00 -0000	[thread overview]
Message-ID: <m3pq28sh30.fsf@redhat.com> (raw)
In-Reply-To: <CAMe9rOqQG8aT3pTeSWfCORCTmk1ys_6PnOaZdi_kH+tc+ztguQ@mail.gmail.com>	(H. J. Lu's message of "Mon, 17 Dec 2012 09:44:26 -0800")

On Monday, December 17 2012, H. J. Lu wrote:

>> Ops, sorry, that code sneaked in apparently.  Here's the new version of
>> the patch.
>>
>
> Can you create a git GDB branch for me to try?

Yep.

The branch is named archer-sergiodj-gcore-prpsinfo on
git://sourceware.org/git/archer.git .

Thanks,

-- 
Sergio

  reply	other threads:[~2012-12-17 17:51 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-17  3:10 Sergio Durigan Junior
2012-12-17 15:43 ` H.J. Lu
2012-12-17 17:41   ` Sergio Durigan Junior
2012-12-17 17:44     ` H.J. Lu
2012-12-17 17:51       ` Sergio Durigan Junior [this message]
2012-12-17 22:01         ` H.J. Lu
2012-12-18  5:47           ` Sergio Durigan Junior
2012-12-18 15:43             ` H.J. Lu
2012-12-18 17:38 ` Jan Kratochvil
2012-12-18 19:19   ` Sergio Durigan Junior
2012-12-18 19:43     ` Jan Kratochvil
2012-12-30  1:50       ` Sergio Durigan Junior
2013-01-01 14:30         ` Jan Kratochvil
2013-01-02 23:32           ` Sergio Durigan Junior
2013-01-03 13:44             ` Jan Kratochvil
2013-01-03 15:46               ` Sergio Durigan Junior
2013-01-04  4:40                 ` Sergio Durigan Junior
2013-01-09 20:49                   ` Sergio Durigan Junior
2013-01-10 18:26                   ` Pedro Alves
2013-01-10 19:47                     ` Sergio Durigan Junior
2013-01-11 15:45                       ` Pedro Alves

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=m3pq28sh30.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=binutils@sourceware.org \
    --cc=gdb-patches@sourceware.org \
    --cc=hjl.tools@gmail.com \
    --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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).