From: Sergio Durigan Junior <sergiodj@redhat.com>
To: Josh Matthews <josh@joshmatthews.net>
Cc: Jan Kratochvil <jan.kratochvil@redhat.com>, gdb-patches@sourceware.org
Subject: Re: [PATCH] Fix darwin build error
Date: Tue, 23 Aug 2011 22:06:00 -0000 [thread overview]
Message-ID: <m3hb574wcl.fsf@redhat.com> (raw)
In-Reply-To: <CAOvJiVWZ3MNCrUQ0a83-cxvv+8pBks2F=coqmvz5w4hqRoNdUA@mail.gmail.com> (Josh Matthews's message of "Tue, 23 Aug 2011 16:47:01 -0400")
Hi Josh,
Josh Matthews <josh@joshmatthews.net> writes:
> Thanks very much everybody. I couldn't find any good guideline for how
> to format the email (and especially the changelot entry) so I cribbed
> off of a random email that was sent recently. It would be quite
> helpful if someone could put together a webpage that listed
Ok, you did good, thanks for the patch.
> 1) what you do with a patch you've written (attach to a bug tracker?
> send to the list?)
> 2) how to format the email
As Jan already mentioned, you can find most of this information in
gdb/CONTRIBUTE. Note that we also follow coding standards (Jan already
mentioned that, too).
> 3) how to do stuff related to copyright assignment
There is an entry abou this on gdb/CONTRIBUTE as well.
I may be wrong here, but in my understanding we take care of this issue
only when the person submits the patch (as you did). I will forward the
procedure to you.
Thanks,
Sergio.
next prev parent reply other threads:[~2011-08-23 22:06 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-22 20:27 Josh Matthews
2011-08-22 22:16 ` Sergio Durigan Junior
2011-08-23 19:43 ` Jan Kratochvil
2011-08-23 20:47 ` Josh Matthews
2011-08-23 20:53 ` Keith Seitz
2011-08-23 20:57 ` Jan Kratochvil
2011-08-23 22:06 ` Sergio Durigan Junior [this message]
2012-01-31 22:00 [PATCH] Fix Darwin " Josh Matthews
2012-02-01 9:27 ` Tristan Gingold
2012-02-01 10:56 ` 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=m3hb574wcl.fsf@redhat.com \
--to=sergiodj@redhat.com \
--cc=gdb-patches@sourceware.org \
--cc=jan.kratochvil@redhat.com \
--cc=josh@joshmatthews.net \
/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