>
> 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