public inbox for gdb-patches@sourceware.org
 help / color / mirror / Atom feed
From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Honggyu Kim <hong.gyu.kim@lge.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v2] Remove duplicated include in gdb directory
Date: Mon, 06 Jan 2014 03:46:00 -0000	[thread overview]
Message-ID: <m3d2k56acm.fsf@redhat.com> (raw)
In-Reply-To: <1388973207-31270-1-git-send-email-hong.gyu.kim@lge.com> (Honggyu	Kim's message of "Mon, 6 Jan 2014 10:53:27 +0900")

On Sunday, January 05 2014, Honggyu Kim wrote:

> This patch simply removes duplicated include statements in gdb directory.
> If there are two duplicated include statements, this patch keeps the first
> include and removes the second include.
> Those are found by checkincludes.pl tool in linux kernel and double checked
> manually once again if the include statements are affected by ifdef macro.

Thanks for the patch, Honggyu.  I believe you have tested it by building
GDB with --enable-targets=all, right?

It needs a ChangeLog (mechanical), and it seems to be simple enough to
be committed without needing a copyright assignment (I don't see your
name in the MAINTAINERS file).

Other than that, let's wait for some maintainer to give the green
light.  BTW, if you want to get started on the process to obtain the
copyright assignment, mail me offlist and I can send you the
instructions.

Thanks,

-- 
Sergio

  reply	other threads:[~2014-01-06  3:46 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 [this message]
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

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=m3d2k56acm.fsf@redhat.com \
    --to=sergiodj@redhat.com \
    --cc=gdb-patches@sourceware.org \
    --cc=hong.gyu.kim@lge.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).