Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Joel Brobecker <brobecker@adacore.com>
To: Honggyu Kim <hong.gyu.kim@lge.com>
Cc: gdb-patches@sourceware.org
Subject: Re: [PATCH v3] Remove duplicated include in gdb directory
Date: Tue, 07 Jan 2014 02:57:00 -0000	[thread overview]
Message-ID: <20140107025701.GF3802@adacore.com> (raw)
In-Reply-To: <006301cf0b4d$dd6d9f50$9848ddf0$@gyu.kim@lge.com>

> I have submitted a new patch with ChangLog modification.  I'm kind of
> new to gdb community so please let me know if you need anything else.
> I appreciate your help.

In that spirit, we kindly request that the text of the ChangeLog
entry be part of the email, rather than in the diff. Having it in
the diff also is fine, I think, if it makes it simpler to send
the patch.

Other than that, no other comment on this patch... Welcome to
the group :).

-- 
Joel


  reply	other threads:[~2014-01-07  2:57 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-07  1:13 Honggyu Kim
2014-01-07  2:12 ` Honggyu Kim
2014-01-07  2:57   ` Joel Brobecker [this message]
2014-01-07  5:07     ` Honggyu Kim
2014-01-07 16:16     ` Sergio Durigan Junior
2014-01-07 16:16   ` Sergio Durigan Junior

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=20140107025701.GF3802@adacore.com \
    --to=brobecker@adacore.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