From: Joel Brobecker <brobecker@adacore.com>
To: Sergio Durigan Junior <sergiodj@redhat.com>
Cc: Tom Tromey <tromey@redhat.com>,
Honggyu Kim <hong.gyu.kim@lge.com>,
gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Remove duplicated include in gdb directory
Date: Tue, 07 Jan 2014 02:44:00 -0000 [thread overview]
Message-ID: <20140107024414.GD3802@adacore.com> (raw)
In-Reply-To: <m3eh4l2ajs.fsf@redhat.com>
> > Sergio> Other than that, let's wait for some maintainer to give the
> > Sergio> green light.
> >
> > You have it.
>
> Thanks, Tom.
>
> Honggyu, could you please provide the ChangeLog for the patch? I can
> push it to the repository when you do that.
Here is a suggestion: If Honggyu were to start the paperwork to assign
past and future changes to GDB, we'd be retroactively covered for this
change as well, and we would not be hindered if future changes come in.
--
Joel
prev parent reply other threads:[~2014-01-07 2:44 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-06 1:53 Honggyu Kim
2014-01-06 3:46 ` Sergio Durigan Junior
2014-01-06 5:13 ` Honggyu Kim
2014-01-06 6:48 ` Honggyu Kim
2014-01-06 14:55 ` Sergio Durigan Junior
2014-01-06 16:37 ` Tom Tromey
2014-01-06 19:08 ` Sergio Durigan Junior
2014-01-07 2:44 ` Joel Brobecker [this message]
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=20140107024414.GD3802@adacore.com \
--to=brobecker@adacore.com \
--cc=gdb-patches@sourceware.org \
--cc=hong.gyu.kim@lge.com \
--cc=sergiodj@redhat.com \
--cc=tromey@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