unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Nils Gillmann <ng0@n0.is>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: guix-devel@gnu.org, Nils Gillmann <ng0@n0.is>
Subject: Re: commit 70f57ae00525f6fc919f62aea647a33b29d28537
Date: Thu, 16 Aug 2018 17:13:35 +0000	[thread overview]
Message-ID: <20180816171335.74g2m2kqtndpvwjm@abyayala> (raw)
In-Reply-To: <87tvnutfak.fsf@elephly.net>

Ricardo Wurmus transcribed 1.1K bytes:
> 
> Hi Nils,
> 
> > Ricardo Wurmus transcribed 227 bytes:
> >>
> >> Nils Gillmann <ng0@n0.is> writes:
> >>
> >> > This commit is okay, but let's all please refrain from doing future
> >> > corrections like this.
> >>
> >> Why?
> >>
> >> I prefer consistency, so I’m happy with Tobias’s change.
> […]
> 
> > Because we also allowed more than one formats so far, including
> > homepages and so forth. We had no formal agreement on any format. I'm
> > okay with doing so once we have a real formal format, but this isn't
> > the case.
> > Discussions and commits to change copyright lines just for the sake of
> > making them look more uniform have a bit of the bikeshed paint feeling.
> > I hardly see a point in changing someones copyright line just for the
> > sake of a (C) or a ©.
> 
> I disagree.  It’s bikeshedding if we start a discussion about which
> symbol is the best.
> 
> In general it is best to use whatever style is already in use in a given
> existing file.  (This also applies to tabs vs spaces for *existing*
> files.)
> 
> Let’s keep using the same copyright symbol that we already use in the
> majority of all files: ©.
> 
> --
> Ricardo
> 

Ok.

      reply	other threads:[~2018-08-16 17:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-08-16  7:30 commit 70f57ae00525f6fc919f62aea647a33b29d28537 Nils Gillmann
2018-08-16 14:53 ` Ricardo Wurmus
2018-08-16 15:56   ` Nils Gillmann
2018-08-16 17:03     ` Ricardo Wurmus
2018-08-16 17:13       ` Nils Gillmann [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=20180816171335.74g2m2kqtndpvwjm@abyayala \
    --to=ng0@n0.is \
    --cc=guix-devel@gnu.org \
    --cc=rekado@elephly.net \
    /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).