From: Kaushal Modi <kaushal.modi@gmail.com>
To: Philippe Vaucher <philippe.vaucher@gmail.com>
Cc: Eli Zaretskii <eliz@gnu.org>, Emacs developers <emacs-devel@gnu.org>
Subject: Re: [PATCH] Remove unused variable `command-debug-status'
Date: Wed, 28 Sep 2016 14:30:47 +0000 [thread overview]
Message-ID: <CAFyQvY2yAQnHmVR1DBCa8uLEsxB1prBbnaFz4LAm1quj7RObug@mail.gmail.com> (raw)
In-Reply-To: <CAGK7Mr7HX3NOQxCs3Aeo6q5+q0_3FTXceYt+UDkOa3u=KZJXkA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2160 bytes --]
On Wed, Sep 28, 2016 at 7:25 AM Philippe Vaucher <philippe.vaucher@gmail.com>
wrote:
> Well, I had to do copyright assignements for ztree, but that was on github
> (https://github.com/fourier/ztree/pull/33).
>
If the copyright assignment was to FSF, then someone having a fencepost
account can confirm if you are on the list. I cannot.
Oh, I did that in the past but I thought that was meant for general bug
> reporting.
>
Based on some recent discussions, the bug report email is meant for
everything: bug reports, feature requests, patch submissions, etc
> Do messages sent to bug-gnu-emacs@gnu.org also end on emacs-devel?
>
No. Those end up on the bug-gnu-emacs mailing list. I believe almost all
core developers subscribe to that. Normally, when I submit a patch, I CC
one or two people whose code I am modifying. (The new vc-region-history
command in emacs 25.1 is really useful for that.) If you do not get a
feedback in about a week or so, it might be useful copying emacs-devel
mailing list and referring them to the bug thread to see if anyone can
review and commit it for you.
> For information, messages like
> https://lists.gnu.org/archive/html/emacs-devel/2016-09/msg00635.html
> don't seem to follow this "patches as bug reports" philosophy.
>
Yeah, the patch submitter needs to ping emacs-devel if they don't get any
response to their update.
> Anyway, I found on
> https://www.kernel.org/doc/Documentation/email-clients.txt that GMail's
> UI is not good to send inline patches, so I'll send them to
> bug-gnu-emacs@gnu.org as attachment instead (that or setup another
> client).
>
I have always sent patches via Google Inbox. They ended up fine. The only
instance where I had to send a patch as an attachment was when it contained
both tab and space characters (I was trying to not mess up the original
whitespace). In such cases, you need to send the patch as an attachment.
Nowadays, with recent commits you will rarely find the tab chars in the
patch diffs (which is a good thing!). So inline patches work just fine.
For reading sanity, I always send emails via Gmail/Inbox without any rich
text formatting.
--
Kaushal Modi
[-- Attachment #2: Type: text/html, Size: 3997 bytes --]
next prev parent reply other threads:[~2016-09-28 14:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-28 10:45 [PATCH] Remove unused variable `command-debug-status' Philippe Vaucher
2016-09-28 11:14 ` Kaushal Modi
2016-09-28 11:24 ` Philippe Vaucher
2016-09-28 14:30 ` Kaushal Modi [this message]
2016-09-28 15:04 ` Philippe Vaucher
2016-10-07 6:01 ` Alexey Veretennikov
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=CAFyQvY2yAQnHmVR1DBCa8uLEsxB1prBbnaFz4LAm1quj7RObug@mail.gmail.com \
--to=kaushal.modi@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=philippe.vaucher@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).