From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Philippe Vaucher Newsgroups: gmane.emacs.devel Subject: Re: [PATCH] Remove unused variable `command-debug-status' Date: Wed, 28 Sep 2016 17:04:52 +0200 Message-ID: References: NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: multipart/alternative; boundary=94eb2c190562b38546053d92b094 X-Trace: blaine.gmane.org 1475075152 26880 195.159.176.226 (28 Sep 2016 15:05:52 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 28 Sep 2016 15:05:52 +0000 (UTC) Cc: Eli Zaretskii , Emacs developers To: Kaushal Modi Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Sep 28 17:05:48 2016 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1bpGQR-0005DJ-PS for ged-emacs-devel@m.gmane.org; Wed, 28 Sep 2016 17:05:36 +0200 Original-Received: from localhost ([::1]:59432 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpGQQ-0003vZ-9q for ged-emacs-devel@m.gmane.org; Wed, 28 Sep 2016 11:05:34 -0400 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45568) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpGQG-0003vO-Ht for emacs-devel@gnu.org; Wed, 28 Sep 2016 11:05:28 -0400 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1bpGQF-0000k2-75 for emacs-devel@gnu.org; Wed, 28 Sep 2016 11:05:24 -0400 Original-Received: from mail-ua0-x234.google.com ([2607:f8b0:400c:c08::234]:34554) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1bpGQF-0000jw-0X; Wed, 28 Sep 2016 11:05:23 -0400 Original-Received: by mail-ua0-x234.google.com with SMTP id l16so21678413uaa.1; Wed, 28 Sep 2016 08:05:22 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=zggtTzccTxo/Y0ZMxOM/89Qb/8S6aLF+96iPPIqrVyg=; b=JE5EmmTlYf7dIdpINQfm5VfFHMRP1vzWCvPW3bYhFOD7ohXReb2iPgvbj26czwoKY2 ndFHgFeutO6rkj4xHTGbbmPrYpm01kMg9/SmuAlUyNSOVwCWupn5nAMHbcUn3lUmvBC0 ZT+WjySGww1OqqZWTrY3SnM1hklziaNLlJ2LkLOCFpjjRATM3lgzjFzZeFFLuN8FkGOz RBnNJRt3uR8BPwUBboEEVTijFNtwpsr2ZKqyuSVOFYRJJ8pmvWk4LlwviCfP09G+gkae lg97jD8h3ZYlOJ9jf7v0MXoeXNu+uyr36+ZCV/HE0WAUjBTvprYx09vxoXMhHY//UFZ+ wTXQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=zggtTzccTxo/Y0ZMxOM/89Qb/8S6aLF+96iPPIqrVyg=; b=k0rHdlX3fWZeFWPD7L/CKd9LwYilomqxhs9yHZdNsnA76OJVQem6nxCmOLC9i/GfbG 9k2uIHg7kDSmk2HogKEiKe8CAyQIRdhAwDRdVDWa6gDzBKOyq/w06DXNBimTHUMKxfzp WywGwP1hemG2dne6UMkO7RuLnyoHF/ezkKVYbHp9CnvyUfALCSCqk4F+ALqBl6YWjGBQ RLl5YPRe9QsUXBYZ7NyLaQVt2iOb5Sg8aY//BcSAkTtjmne7S248Hx+2O9GhocdUYoz4 K5GlBKHJsdIor9CXyN/kbFXx8NCsRfqF2Y24hh8gJEPIXcIBh4N15rcsBk2VfVaS/xNl Jc1w== X-Gm-Message-State: AA6/9RnkCk+YTZaRYVsFh87etFjV5n5RyK6C+AA0g2kziZIaLU+9Tv9w7wUi+Zg89i//xcoeXA+lsTNZOBcU6g== X-Received: by 10.176.82.168 with SMTP id v37mr802621uav.72.1475075122624; Wed, 28 Sep 2016 08:05:22 -0700 (PDT) Original-Received: by 10.103.0.197 with HTTP; Wed, 28 Sep 2016 08:04:52 -0700 (PDT) In-Reply-To: X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2607:f8b0:400c:c08::234 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:207863 Archived-At: --94eb2c190562b38546053d92b094 Content-Type: text/plain; charset=UTF-8 > > 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 --94eb2c190562b38546053d92b094 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable
Based on some recent discussions, the bug report email is meant for everyt= hing: bug reports, feature requests, patch submissions, etc

I won= der what's left for emacs-devel then ;)

=C2=A0= =C2=A0
Do messages se= nt to bug-gnu-em= acs@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, wh= en 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 copyin= g emacs-devel mailing list and referring them to the bug thread to see if a= nyone can review and commit it for you.
=
Alright, thanks for the detailed information! Very appreciat= ed.
vc-region-history is nice! until now for that I used magit-bl= ame & git-timemachine.

=C2=A0
I have= always sent patches via Google Inbox. They ended up fine. The only instanc= e where I had to send a patch as an attachment was when it contained both t= ab and space characters (I was trying to not mess up the original whitespac= e). In such cases, you need to send the patch as an attachment. Nowadays, w= ith recent commits you will rarely find the tab chars in the patch diffs (w= hich is a good thing!). So inline patches work just fine.
=

Well, I guess as long as word-wrap does no= t mangle your patch you are fine sending them inline.

<= div>Kind regards,
Philippe
--94eb2c190562b38546053d92b094--