From: Alexey Veretennikov <alexey.veretennikov@gmail.com>
To: Philippe Vaucher <philippe.vaucher@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>,
Kaushal Modi <kaushal.modi@gmail.com>
Subject: Re: [PATCH] Remove unused variable `command-debug-status'
Date: Fri, 07 Oct 2016 08:01:37 +0200 [thread overview]
Message-ID: <m2zimgsnni.fsf@MacBook-Pro-2.lan> (raw)
In-Reply-To: <CAGK7Mr7HX3NOQxCs3Aeo6q5+q0_3FTXceYt+UDkOa3u=KZJXkA@mail.gmail.com> (Philippe Vaucher's message of "Wed, 28 Sep 2016 13:24:41 +0200")
Hi,
Philippe has signed papers and it is confirmed by JohnW.
Thanks!
Philippe Vaucher <philippe.vaucher@gmail.com> writes:
> I already did the copyright assignment dance and it was accepted &
> sent to me the 2016-09-07, do I need to send the confirmation to
> someone in order to post here?
>
>
> When I sent my first patch, I asked the person who helped commit that to look up my name in the
> list of people who have assigned their copyright.
>
>
> Well, I had to do copyright assignements for ztree, but that was on github
> (https://github.com/fourier/ztree/pull/33). Maybe @fourier will recognize himself and warrant me then :-)
> (I'm Silex).
>
> The patches should be sent as bug reports. That way, the patch and the reasoning behind it stays
> together in a clean bug thread. Also the commit to master can then refer to that (Bug#NNNNN). So,
> no guesswork is involved if someone wants to understand why a particular commit was made.
>
>
> Oh, I did that in the past but I thought that was meant for general bug reporting. Do messages sent to
> bug-gnu-emacs@gnu.org also end on emacs-devel? 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.
>
> 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).
>
> Thanks!
> Philippe
>
--
Br,
/Alexey
prev parent reply other threads:[~2016-10-07 6:01 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
2016-10-07 6:01 ` Alexey Veretennikov [this message]
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=m2zimgsnni.fsf@MacBook-Pro-2.lan \
--to=alexey.veretennikov@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=kaushal.modi@gmail.com \
--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).