From: ludo@gnu.org (Ludovic Courtès)
To: Pierre Neidhardt <ambrevar@gmail.com>
Cc: help-guix <help-guix@gnu.org>
Subject: How to announce important changes
Date: Wed, 20 Jun 2018 22:41:58 +0200 [thread overview]
Message-ID: <87sh5hqjft.fsf_-_@gnu.org> (raw)
In-Reply-To: <87a7rrj6t4.fsf@gmail.com> (Pierre Neidhardt's message of "Tue, 19 Jun 2018 14:32:07 +0200")
Hello,
Pierre Neidhardt <ambrevar@gmail.com> skribis:
> OK, I get it now. I had missed that message about the PATH.
>
> I think those kinds of breakage would deserve some proper annoucements,
> either on the mailing list or on the website.
>
> What do you people think?
I agree. The patch for the new ‘guix pull’ was discussed 2-3 weeks
before being applied, and the principle was discussed even earlier than
this, but for someone not following the mailing list, I understand this
is a problem.
Perhaps it’s time for an announcement mailing list, and/or blog posts.
What do people think?
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-06-20 20:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-17 20:24 Can't configure guix, no guile-sqlite3 Thorsten Wilms
2018-06-18 19:58 ` Ludovic Courtès
2018-06-18 20:12 ` Pierre Neidhardt
2018-06-19 10:26 ` swedebugia
2018-06-19 10:32 ` Pierre Neidhardt
2018-06-19 12:27 ` swedebugia
2018-06-19 12:32 ` Pierre Neidhardt
2018-06-20 20:41 ` Ludovic Courtès [this message]
2018-06-20 22:05 ` How to announce important changes Pierre Neidhardt
2018-06-21 0:39 ` myglc2
2018-06-21 10:52 ` Ricardo Wurmus
2018-06-19 10:33 ` Can't configure guix, no guile-sqlite3 Thorsten Wilms
2018-07-23 19:51 ` Thorsten Wilms
2018-08-02 7:12 ` Chris Marusich
2018-08-02 11:40 ` Thorsten Wilms
2018-08-02 12:18 ` Ricardo Wurmus
2018-08-02 13:21 ` Thorsten Wilms
2018-08-19 21:31 ` Maxim Cournoyer
2018-08-23 20:03 ` Thorsten Wilms
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=87sh5hqjft.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=ambrevar@gmail.com \
--cc=help-guix@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.