From: Andreas Rottmann <a.rottmann@gmx.at>
To: Glenn Morris <rgm@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: where to send patches [was Re: [PATCH] Allow passing frame parameters to emacsclient]
Date: Mon, 07 Mar 2011 23:29:19 +0100 [thread overview]
Message-ID: <878vwqmuo0.fsf@vir.lan> (raw)
In-Reply-To: <kczkp6obbf.fsf@fencepost.gnu.org> (Glenn Morris's message of "Mon, 07 Mar 2011 16:44:20 -0500")
Glenn Morris <rgm@gnu.org> writes:
> Andreas Rottmann wrote:
>
>> This is the first patch I submit for Emacs, so I hope I followed all the
>> rules :-). I initially submitted a now-stale version of the patch as a
>> bugreport[0] -- I assume I should close this, as patches are to be
>> submitted and discussed on this mailinglist (or bug-gnu-emacs@gnu.org),
>> right?
>
> Thank you for writing a patch, and I'm sorry no-one has really replied
> about it yet, but why not just followup to your original report with a
> revised version? How is anyone reading the report supposed to know a
> newer version exists?
>
Yeah, my bad. I was a bit confused about where to send the patch.
> I forwarded the revised version to the report.
>
Thanks! There's a minor conflict in NEWS now, I'll attach an updated
revision of the patch to the bug report.
> I strongly advise everybody sending in patches that add features or
> fix bugs to send them to bug-gnu-emacs (which should really be thought
> of as the bug and/or feature list). I feel like I've said this a lot,
> so people either disagree or aren't noticing.
>
I'll certainly send future patches to bug-gnu-emacs. If this is the
clear preference, perhaps etc/CONTRIBUTE should be changed to mention
only bug-gnu-emacs.
> So I'll probably stop saying it. Forwarding things there is a bit of a
> chore, and I may not always bother. I know emacs-devel has more
> traffic, but I'm not sure that indicates much.
>
> The bug-gnu-emacs list is coupled with a tracking system that makes
> patches much easier to locate, even years later. I'm not aware of anyone
> searching emacs-devel for old patches to apply. Maybe people are using
> the "keep in their INBOX" method of tracking things though.
Regards & thanks again, Rotty
--
Andreas Rottmann -- <http://rotty.yi.org/>
next prev parent reply other threads:[~2011-03-07 22:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-26 17:32 [PATCH] Allow passing frame parameters to emacsclient Andreas Rottmann
2011-03-07 21:44 ` where to send patches [was Re: [PATCH] Allow passing frame parameters to emacsclient] Glenn Morris
2011-03-07 22:29 ` Andreas Rottmann [this message]
2011-03-08 2:05 ` Stefan Monnier
2011-03-09 19:50 ` where to send patches Glenn Morris
2011-03-09 20:24 ` Chong Yidong
2011-03-09 20:31 ` Glenn Morris
2011-03-10 2:26 ` Stefan Monnier
2011-03-20 23:06 ` Wojciech Meyer
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=878vwqmuo0.fsf@vir.lan \
--to=a.rottmann@gmx.at \
--cc=emacs-devel@gnu.org \
--cc=rgm@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.