From: Philippe Vaucher <philippe.vaucher@gmail.com>
To: Kaushal Modi <kaushal.modi@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 17:04:52 +0200 [thread overview]
Message-ID: <CAGK7Mr5XhgvOLqeRfRb5hJfTEw=NCZco2Cu_snezV7CnDBjirw@mail.gmail.com> (raw)
In-Reply-To: <CAFyQvY2yAQnHmVR1DBCa8uLEsxB1prBbnaFz4LAm1quj7RObug@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1467 bytes --]
>
> Based on some recent discussions, the bug report email is meant for
> everything: bug reports, feature requests, patch submissions, etc
>
I wonder what's left for emacs-devel then ;)
> 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.
>
Alright, thanks for the detailed information! Very appreciated.
vc-region-history is nice! until now for that I used magit-blame &
git-timemachine.
> 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.
>
Well, I guess as long as word-wrap does not mangle your patch you are fine
sending them inline.
Kind regards,
Philippe
[-- Attachment #2: Type: text/html, Size: 2552 bytes --]
next prev parent reply other threads:[~2016-09-28 15:04 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
2016-09-28 15:04 ` Philippe Vaucher [this message]
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='CAGK7Mr5XhgvOLqeRfRb5hJfTEw=NCZco2Cu_snezV7CnDBjirw@mail.gmail.com' \
--to=philippe.vaucher@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@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).