all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: ludo@gnu.org (Ludovic Courtès)
To: Federico Beffa <beffa@ieee.org>
Cc: Guix-devel <guix-devel@gnu.org>, Alex Kost <alezost@gmail.com>
Subject: Re: [PATCH 3/5] build: Add 'emacs-build-system'
Date: Thu, 25 Jun 2015 13:57:09 +0200	[thread overview]
Message-ID: <87pp4khuga.fsf@gnu.org> (raw)
In-Reply-To: <CAKrPhPMzmdAcO2mDJ_oRTv-8UHK10Cx8OnTU1wNeTBJmOJ+3ng@mail.gmail.com> (Federico Beffa's message of "Tue, 23 Jun 2015 08:51:52 +0200")

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’s mostly that no-trailing-whitespace is a simple canonical form.
Having everyone follow it makes sure we don’t run into annoying patch
conflicts due to whitespace, nor “noisy patches” that remove trailing
spaces here and there.

Ludo’.

  reply	other threads:[~2015-06-25 11:57 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-21  8:31 [PATCH 3/5] build: Add 'emacs-build-system' Federico Beffa
2015-06-21 20:40 ` Alex Kost
2015-06-22  8:51   ` Federico Beffa
2015-06-22 11:49     ` Mathieu Lirzin
2015-06-22 17:59     ` Alex Kost
2015-06-22 19:33       ` Federico Beffa
2015-06-22 19:40         ` Thompson, David
2015-06-23  6:51           ` Federico Beffa
2015-06-25 11:57             ` Ludovic Courtès [this message]
2015-06-25 18:39               ` Federico Beffa
2015-06-23 11:57         ` Alex Kost
2015-06-24 16:12           ` Federico Beffa
2015-06-25 12:33             ` Ludovic Courtès
2015-06-25 18:36               ` Federico Beffa
2015-06-27  9:59                 ` Ludovic Courtès
2015-07-06 17:47 ` Alex Kost
  -- strict thread matches above, loose matches on Subject: below --
2015-07-07  7:21 Federico Beffa
2015-07-07 16:58 ` Alex Kost
2015-07-08 20:22   ` Federico Beffa
2015-07-09  8:51     ` Alex Kost
2015-07-09 20:41       ` Federico Beffa
2015-07-10  6:47         ` Alex Kost
2015-07-10  7:43           ` Federico Beffa
2015-07-15 21:52           ` Ludovic Courtès

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87pp4khuga.fsf@gnu.org \
    --to=ludo@gnu.org \
    --cc=alezost@gmail.com \
    --cc=beffa@ieee.org \
    --cc=guix-devel@gnu.org \
    /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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.