From mboxrd@z Thu Jan  1 00:00:00 1970
From: Federico Beffa <beffa@ieee.org>
Subject: Re: [PATCH 3/5] build: Add 'emacs-build-system'
Date: Thu, 25 Jun 2015 20:39:55 +0200
Message-ID: <CAKrPhPP1sZxRy2VYGyNtB8PPpzViOdbprd27wOUuG9NZcHh4Bg@mail.gmail.com>
References: <CAKrPhPOqhwu2LrQiYTZMApbTVZxTXvWdmJxhB9vtQGqHshsiAg@mail.gmail.com>
	<87twu06bhk.fsf@gmail.com>
	<CAKrPhPNkOLzx8ex8O1Qb=HLZRo+=cNHiZFaPgnoenajMMNvorg@mail.gmail.com>
	<87si9jsjyj.fsf@gmail.com>
	<CAKrPhPOcd6iBR3AXfp2aTn-z0opGo9HHX_9kScbgWZVmB7s9-g@mail.gmail.com>
	<CAJ=RwfZpj484Cbht1PxG_nLrutGwf0AkLULdqj5y9YpekyCXpA@mail.gmail.com>
	<CAKrPhPMzmdAcO2mDJ_oRTv-8UHK10Cx8OnTU1wNeTBJmOJ+3ng@mail.gmail.com>
	<87pp4khuga.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:59651)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <federico.beffa@gmail.com>) id 1Z8C44-0007Yw-U9
	for guix-devel@gnu.org; Thu, 25 Jun 2015 14:39:57 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <federico.beffa@gmail.com>) id 1Z8C43-0008LU-Uq
	for guix-devel@gnu.org; Thu, 25 Jun 2015 14:39:56 -0400
In-Reply-To: <87pp4khuga.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
To: =?UTF-8?Q?Ludovic_Court=C3=A8s?= <ludo@gnu.org>
Cc: Guix-devel <guix-devel@gnu.org>, Alex Kost <alezost@gmail.com>

On Thu, Jun 25, 2015 at 1:57 PM, Ludovic Court=C3=A8s <ludo@gnu.org> wrote:
> Federico Beffa <beffa@ieee.org> skribis:
>
>> On Mon, Jun 22, 2015 at 9:40 PM, Thompson, David
>> <dthompson2@worcester.edu> wrote:
>>> On Mon, Jun 22, 2015 at 3:33 PM, Federico Beffa <beffa@ieee.org> wrote:
>>>>
>>>> But, my question was NOT: how can I see white spaces. Rather: is there
>>>> a Guix coding style "rule" which states that white spaces there are
>>>> undesired.
>>>>
>>>> I personally prefer to have them, because then, if I use M-up/down, I
>>>> move to the beginning/end of a whole top-level block, without stopping
>>>> at internal points and that's what I want most of the time.
>>>>
>>>> So, these spaces are not just coding artifacts, but have some use.
>>>
>>> There should be *no* trailing whitespace in submitted patches, and we
>>> should add a note about it to our contribution guidelines if it's not
>>> already there.
>
> +1
>
>> OK, I will delete those spaces then. But, I'm curious about the
>> rationale for such a rule.
>
> It=E2=80=99s mostly that no-trailing-whitespace is a simple canonical for=
m.
> Having everyone follow it makes sure we don=E2=80=99t run into annoying p=
atch
> conflicts due to whitespace, nor =E2=80=9Cnoisy patches=E2=80=9D that rem=
ove trailing
> spaces here and there.

Makes sense. Thanks for the explanation.

Fede