From: ludo@gnu.org (Ludovic Courtès)
To: Marius Bakke <mbakke@fastmail.com>
Cc: guix-devel@gnu.org
Subject: Re: 01/01: gnu: cmake: Delete Emacs library.
Date: Mon, 28 May 2018 11:41:39 +0200 [thread overview]
Message-ID: <87muwk2k30.fsf@gnu.org> (raw)
In-Reply-To: <87y3g6edxd.fsf@fastmail.com> (Marius Bakke's message of "Sat, 26 May 2018 15:37:02 +0200")
Hello Marius & all,
Marius Bakke <mbakke@fastmail.com> skribis:
> Good idea. It would be good to clarify that this also applies for
> 'staging'. What do you think about this instead?
>
> 1 file changed, 9 insertions(+), 2 deletions(-)
> doc/contributing.texi | 11 +++++++++--
The patch LGTM!
> +@c TODO: It would be good with badges on the website that tracks these
> +@c branches. Or maybe even a status page.
I agree! I admit I sometimes have a hard time determining the current
status of every branch (for instance I’m not sure what’s up with
‘staging’ at the moment…)
Perhaps a lo-tech thing would be to have more frequent reminders on the
mailing list of the status of each branch, also as a way to solicitate
contributions on these branches.
I really think we need to have someone responsible for those rebuild
cycles, and to arrange to hand over reponsibilities to a different
person after each cycle or so.
Thanks,
Ludo’.
next prev parent reply other threads:[~2018-05-28 9:41 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20180522141738.8231.26687@vcs0.savannah.gnu.org>
[not found] ` <20180522141741.641D120711@vcs0.savannah.gnu.org>
2018-05-22 18:43 ` 01/01: gnu: cmake: Delete Emacs library Mark H Weaver
2018-05-23 16:10 ` Oleg Pykhalov
2018-05-24 1:35 ` Mark H Weaver
2018-05-25 10:02 ` Oleg Pykhalov
2018-05-26 13:37 ` Marius Bakke
2018-05-28 9:41 ` Ludovic Courtès [this message]
2018-05-28 9:55 ` Vincent Legoll
2018-06-16 19:44 ` Marius Bakke
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=87muwk2k30.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=guix-devel@gnu.org \
--cc=mbakke@fastmail.com \
/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).