From: Kaushal Modi <kaushal.modi@gmail.com>
To: John Shahid <jvshahid@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: Where should I send patches
Date: Thu, 31 May 2018 13:27:11 -0400 [thread overview]
Message-ID: <CAFyQvY0vzfJQFsVeK-AY4PwkAbkFgTVGoTNd-YV2WEDv8GWayw@mail.gmail.com> (raw)
In-Reply-To: <87o9gveqsm.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1107 bytes --]
I am just a minor (may be micro) contributor to Emacs. But still I have few
comments:
On Thu, May 31, 2018 at 12:25 PM John Shahid <jvshahid@gmail.com> wrote:
>
> I was little confused given that I received no replies on my bug
> report[1] , which admittedly was sent last night.
"last night"? That's a lot of expectation. Realize that here we are
collaborating with folks all around the world, different time zones. In
general, I wait for 4 days or so before pinging back on that same "bug
report" (quoting that because that report could also be a feature request
or a patch, or anything).
> What is more confusing
> is the fact that I see patches being discussed on this
> (emacs-devel@gnu.org) mailing list instead of bug-gnu-emacs@gnu.org.
Usually patch discussion comes to emacs-devel if the discussion doesn't
resolve on that bug thread itself, or if more user feedback is needed.
> Out of curiosity if I have a patch to submit which list should I use ?
>
> [1] http://debbugs.gnu.org/cgi/bugreport.cgi?bug=31662
>
I would use the same bug thread for patch proposals too.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 2083 bytes --]
next prev parent reply other threads:[~2018-05-31 17:27 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-31 16:24 Where should I send patches John Shahid
2018-05-31 17:27 ` Kaushal Modi [this message]
2018-05-31 17:33 ` John Shahid
2018-05-31 18:54 ` Eli Zaretskii
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAFyQvY0vzfJQFsVeK-AY4PwkAbkFgTVGoTNd-YV2WEDv8GWayw@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jvshahid@gmail.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).