From: "Léo Le Bouter" <lle-bout@zaclys.net>
To: Mark H Weaver <mhw@netris.org>,
Raghav Gururajan <rg@raghavgururajan.name>,
Guix Devel <guix-devel@gnu.org>
Subject: Re: GNOME 40
Date: Mon, 29 Mar 2021 23:33:47 +0200 [thread overview]
Message-ID: <9534f336f342a3275eb0ff92970683c89de74880.camel@zaclys.net> (raw)
In-Reply-To: <878s67dmwn.fsf@netris.org>
[-- Attachment #1: Type: text/plain, Size: 381 bytes --]
On Sun, 2021-03-28 at 16:48 -0400, Mark H Weaver wrote:
> How is it more flexible than a "wip-*" branch on Savannah?
>
> Thanks,
> Mark
Because as the GNU Guix project we have no control on the forge to
catter it to our own needs, because there is bureaucracy involved with
approving new committers so they can work on wip branches (shouldnt be
necessary).
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-03-29 21:34 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-28 13:19 GNOME 40 Raghav Gururajan
2021-03-28 15:16 ` Léo Le Bouter
2021-03-28 20:48 ` Mark H Weaver
2021-03-29 7:38 ` Christopher Baines
2021-03-29 23:02 ` GNOME 40 work should be done on Savannah (was: Re: GNOME 40) Mark H Weaver
2021-03-29 23:17 ` Léo Le Bouter
2021-03-30 6:41 ` Mark H Weaver
2021-03-30 11:12 ` zimoun
2021-03-30 23:50 ` Léo Le Bouter
2021-03-30 12:12 ` GNOME 40 work should be done on Savannah Ludovic Courtès
2021-03-31 0:06 ` Léo Le Bouter
2021-03-31 1:55 ` Mark H Weaver
2021-03-31 2:08 ` Léo Le Bouter
2021-03-31 0:16 ` Léo Le Bouter
2021-03-30 6:53 ` GNOME 40 work should be done on Savannah (was: Re: GNOME 40) Christopher Baines
2021-03-29 21:33 ` Léo Le Bouter [this message]
2021-03-31 14:05 ` GNOME 40 宋文武
2021-03-29 11:41 ` Raghav Gururajan
[not found] ` <67c5aac2-2669-62dc-a82a-16c2bf9b554a@raghavgururajan.name>
2021-04-07 19:10 ` Raghav Gururajan
2021-04-10 7:09 ` 宋文武
2021-04-13 20:27 ` Mark H Weaver
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=9534f336f342a3275eb0ff92970683c89de74880.camel@zaclys.net \
--to=lle-bout@zaclys.net \
--cc=guix-devel@gnu.org \
--cc=mhw@netris.org \
--cc=rg@raghavgururajan.name \
/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).