From: Joel Brobecker <brobecker@adacore.com>
To: JuYoung Kim <j0.kim@samsung.com>
Cc: Eli Zaretskii <eliz@gnu.org>,
"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: Re: [patch]change dwarf2_start_subfile() to adapt inappropriate dir name
Date: Mon, 15 Nov 2010 16:58:00 -0000 [thread overview]
Message-ID: <20101115165834.GA4434@adacore.com> (raw)
In-Reply-To: <13428716.22191289802305139.JavaMail.weblogic@epml17>
[Would you like to be called "Kim", or "JuYoung"?]
> I hope this code is proper to the standard, and no more to be fixed.
> Please, tell me what is the next step that I should do for applying to
> the real source code.
For proper submission of patches to the GDB project, please take a look
at the file named gdb/CONTRIBUTE. For the patch, most of us prefer
unified diffs (use "diff -u" as opposed to "diff -c").
Last question: Is your mailer capable of keeping the email threading
information?
--
Joel
next prev parent reply other threads:[~2010-11-15 16:58 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-15 6:25 JuYoung Kim
2010-11-15 16:58 ` Joel Brobecker [this message]
2010-11-15 18:05 ` Nathan Froyd
2010-11-15 18:34 ` Eli Zaretskii
2010-11-23 20:47 ` Tom Tromey
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=20101115165834.GA4434@adacore.com \
--to=brobecker@adacore.com \
--cc=eliz@gnu.org \
--cc=gdb-patches@sourceware.org \
--cc=j0.kim@samsung.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).