From: ng0 <ngillmann@runbox.com>
To: "Ludovic Courtès" <ludo@gnu.org>, "Alex Kost" <alezost@gmail.com>
Cc: guix-devel@gnu.org
Subject: Re: Cosmetical change: remove inconsistent "$file ends here"?
Date: Thu, 06 Oct 2016 19:18:30 +0000 [thread overview]
Message-ID: <87vax5e16h.fsf@we.make.ritual.n0.is> (raw)
In-Reply-To: <87zims4dwu.fsf@gnu.org>
Ludovic Courtès <ludo@gnu.org> writes:
> Alex Kost <alezost@gmail.com> skribis:
>
>> ng0 (2016-09-24 20:00 +0000) wrote:
>>
>>> We should either be consistent with this in all files or remove this
>>> altogether in my opinion.
>>>
>>>> ng0@shadowwalker ~/src/guix/guix-no-changes$ egrep -nr "ends here"
>>>> gnu/build/vm.scm:323:;;; vm.scm ends here
>> ...
>>> What do you think?
>>
>> I don't know what the original purpose of this convention is, it was
>> probably invented in those ancient times when dinosaurs walked by
>> streets, but I kinda like these "ends here" things :-)
>
> Yeah, I add them occasionally out of habit, but it’s not useful.
>
>> Anyway, I vote for leaving them and adding the missing ones.
>
> I vote for the status quo. :-) There’s not much value in spending time
> either way IMO.
>
> Ludo’.
>
Okay, let's keep it this way. There's nothing to be gained from this.
prev parent reply other threads:[~2016-10-06 19:19 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 20:00 Cosmetical change: remove inconsistent "$file ends here"? ng0
2016-09-25 8:30 ` Alex Kost
2016-09-25 9:21 ` ng0
2016-09-26 8:32 ` Christopher Allan Webber
2016-09-26 8:45 ` Andy Wingo
2016-09-25 9:32 ` John Darrington
2016-09-25 9:38 ` Danny Milosavljevic
2016-09-25 17:45 ` Hartmut Goebel
2016-09-25 17:55 ` Vincent Legoll
2016-09-25 17:59 ` John Darrington
2016-09-28 8:38 ` Ludovic Courtès
2016-10-06 19:18 ` ng0 [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://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87vax5e16h.fsf@we.make.ritual.n0.is \
--to=ngillmann@runbox.com \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=ludo@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 public inbox
https://git.savannah.gnu.org/cgit/guix.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).