From: Phil Muldoon <pmuldoon@redhat.com>
To: Abhijit Halder <abhijit.k.halder@gmail.com>
Cc: gdb-patches@sourceware.org
Subject: Re: Query: About process
Date: Mon, 01 Aug 2011 10:05:00 -0000 [thread overview]
Message-ID: <m362mhsazy.fsf@redhat.com> (raw)
In-Reply-To: <CAOhZP9xOfjWztyJJG5BDimrrn2379rNGXJOSdmSvBfMCE08Whw@mail.gmail.com> (Abhijit Halder's message of "Mon, 1 Aug 2011 15:19:16 +0530")
Abhijit Halder <abhijit.k.halder@gmail.com> writes:
> Hi,
>
> I am pretty new in this community. Just curious to know whether I will
> get any notification if my patch get accepted or rejected.
Your patch will get reviewed (by anybody, but normally by a
maintainer). They may require changes to the patch.
Only a maintainer can grant you approval to commit your patch. The
CONTRIBUTE file in the gdb/ source directory gives a good overview.
Sometimes, patches can be missed. I generally "ping" patches after a
week if no review has been forthcoming. Sometimes the maintainer
work-load is very high, so some things get missed/forgotten. It is
perfectly acceptable to "ping" a patch after a reasonable time, and you
will not be breaking any etiquette by doing so.
Finally, questions like this generally go to gdb@sourceware.org, and
patch discussion about actual patches to gdb-patches@sourceware.org.
These rules are very loosely applied, so you have done nothing wrong. I
just thought this would be a good time to point out the other list!
Cheers
Phil
next prev parent reply other threads:[~2011-08-01 10:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-01 9:49 Abhijit Halder
2011-08-01 10:05 ` Phil Muldoon [this message]
2011-08-01 10:10 ` Abhijit Halder
2011-08-02 4:01 ` Sergio Durigan Junior
2011-08-02 6:56 ` Abhijit Halder
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=m362mhsazy.fsf@redhat.com \
--to=pmuldoon@redhat.com \
--cc=abhijit.k.halder@gmail.com \
--cc=gdb-patches@sourceware.org \
/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