From: Mark H Weaver <mhw@netris.org>
To: "Léo Le Bouter" <lle-bout@zaclys.net>,
"Raghav Gururajan" <rg@raghavgururajan.name>,
"Guix Devel" <guix-devel@gnu.org>
Subject: Re: GNOME 40
Date: Sun, 28 Mar 2021 16:48:45 -0400 [thread overview]
Message-ID: <878s67dmwn.fsf@netris.org> (raw)
In-Reply-To: <0323e477b9226759445ad7c58bad134fcff4bc40.camel@zaclys.net>
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?
Thanks,
Mark
next prev parent reply other threads:[~2021-03-28 20:50 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 [this message]
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 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=878s67dmwn.fsf@netris.org \
--to=mhw@netris.org \
--cc=guix-devel@gnu.org \
--cc=lle-bout@zaclys.net \
--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 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.