unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Christopher Baines <mail@cbaines.net>
To: Mark H Weaver <mhw@netris.org>
Cc: guix-devel@gnu.org
Subject: Re: GNOME 40
Date: Mon, 29 Mar 2021 08:38:00 +0100	[thread overview]
Message-ID: <878s669zqf.fsf@cbaines.net> (raw)
In-Reply-To: <878s67dmwn.fsf@netris.org>

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


Mark H Weaver <mhw@netris.org> writes:

> Léo Le Bouter <lle-bout@zaclys.net> writes:
>
>> If anyone is curious of the work or wants to participate, we are
>> working there:
>> https://git.guix-patches.cbaines.net/guix-patches/log/?h=wip-gnome-40
>>
>> The branch is based on core-updates and we will rebase it every now and
>> then, as well as merging patches to official core-updates as we feel it
>> is necessary.
>>
>> cbaines gave us access to the git repo, it's not official so it's more
>> flexible,
>
> How is it more flexible than a "wip-*" branch on Savannah?

I wouldn't use quite the same words as Léo, but from my perspective,
controlling access to particular branches (master, staging,
core-updates, ...) on Savannah is a good thing, as it reduces risk. I
don't think that's relevant for all branches though, it would be better
if more people could collaborate through wip-* branches (if that's
useful to them).

As Savannah doesn't allow for access control per branch (or even per
project repository), currently to give someone access to anything, you
have to give them access to everything. Maybe that's possible to
improve, but using some other Git repository hosted elsewhere is one
workaround.

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

  reply	other threads:[~2021-03-29  7:38 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 [this message]
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     ` GNOME 40 Léo Le Bouter
2021-03-31 14:05       ` 宋文武
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=878s669zqf.fsf@cbaines.net \
    --to=mail@cbaines.net \
    --cc=guix-devel@gnu.org \
    --cc=mhw@netris.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).