unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Tobias Geerinckx-Rice <me@tobias.gr>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Deliver important Guix changes to users, please
Date: Tue, 16 Apr 2019 20:19:26 +0200	[thread overview]
Message-ID: <878sw9ak41.fsf@nckx> (raw)
In-Reply-To: <8736mjo29k.fsf@gnu.org>

[-- Attachment #1: Type: text/plain, Size: 992 bytes --]

Ludo', Guix,

As your friendly neighbourhood update bot, I read a lot of change 
logs.  The worst are the one-log text file with ’lol use git now, 
change logs are obsolete!1’.  Utterly clueless, distressingly 
common.

The best ones are usually called NEWS for some reason (go GNU!) 
and are manually maintained, in sync with the code changes but not 
forced on top of them; using git but not abusing it.

Ludovic Courtès wrote:
> I suppose we could use some specially-formatted Git commits to 
> pass
> messages to users.  I’m afraid it would be hard to get those 
> messages
> translated.

I beg you not to do this, even as fodder for a friendly front end. 
Just use a structured text file.  Add dates.  Affected packages. 
Metadata.  Hell, use sexps if you like.  Fix typos/add caveats to 
old news items when needed, not through errata commits.  Don't 
confuse git log with a log like some people confuse git blame with 
comments.

That is all,

T G-R

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]

  parent reply	other threads:[~2019-04-16 18:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-04-14 11:25 Deliver important Guix changes to users, please znavko
2019-04-15 12:56 ` Ludovic Courtès
2019-04-16  3:55   ` Amin Bandali
2019-04-16 19:15     ` Brett Gilio
2019-04-16 18:19   ` Tobias Geerinckx-Rice [this message]
2019-04-16 18:27     ` Tobias Geerinckx-Rice
2019-04-16 20:30     ` Ludovic Courtès
2019-04-16 21:38       ` Tobias Geerinckx-Rice
2019-04-16 17:21 ` znavko

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=878sw9ak41.fsf@nckx \
    --to=me@tobias.gr \
    --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).