From: "Ludovic Courtès" <ludo@gnu.org>
To: Tobias Geerinckx-Rice <me@tobias.gr>
Cc: guix-devel@gnu.org
Subject: Re: Deliver important Guix changes to users, please
Date: Tue, 16 Apr 2019 22:30:35 +0200 [thread overview]
Message-ID: <87bm15d76c.fsf@gnu.org> (raw)
In-Reply-To: <878sw9ak41.fsf@nckx> (Tobias Geerinckx-Rice's message of "Tue, 16 Apr 2019 20:19:26 +0200")
Hello,
Tobias Geerinckx-Rice <me@tobias.gr> skribis:
> 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.
The interesting part here is that commits are anchored in the version
control history. Thus, you could easily tell whether a news item is
relevant or not.
If you store news separately, well I guess you could just write the
commit to which the news item applies.
Hmm, maybe you’re right!
So we could have, say:
.news/[0-9]+.news (every other file would be ignored)
and then some sexp format, say:
(news
(entry
(title "GDM is now the default")
(commit "cabba9e")
(body "Hey, GDM’s in the house!"))
(entry
(title "News are here")
…))
and we could maybe even have a PO file for this.
How does that sound?
(Probably post 1.0, but worth discussing.)
Ludo’.
next prev parent reply other threads:[~2019-04-16 20:30 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
2019-04-16 18:27 ` Tobias Geerinckx-Rice
2019-04-16 20:30 ` Ludovic Courtès [this message]
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=87bm15d76c.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=me@tobias.gr \
/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).