From: Raghav Gururajan <rg@raghavgururajan.name>
To: Ricardo Wurmus <rekado@elephly.net>
Cc: "Léo Le Bouter" <lle-bout@zaclys.net>,
"Danny Milosavljevic" <dannym@scratchpost.org>,
guix-devel@gnu.org
Subject: Re: GNOME 3.34 in GNU Guix and security
Date: Thu, 11 Mar 2021 04:17:51 -0500 [thread overview]
Message-ID: <2cd5f69e-9ace-a5c5-ab69-e2e560fc2953@raghavgururajan.name> (raw)
In-Reply-To: <87czw6qcl6.fsf@elephly.net>
[-- Attachment #1.1: Type: text/plain, Size: 891 bytes --]
Hi Ricardo!
> Thanks for the update!
Also, then reason GNOME work got messed up is that, in wip-desktop, [1]
I was not just working gnome packages, but also its dependencies [2]
Work involved not just updates, but also improvements. This kinda
complicated the "update stuff" norm.
> I think that ci.guix.gnu.org should be capable of building your branch.
On a note, I have put more work on myself. When I was working on
wip-desktop, I made larget commits instead of 'one change per commit'.
So after a discussion, I was asked to split them into smaller chunks. So
I need to get #42958 out of the way.
> Excellent! Let me know if there’s anything I can do to assist.
Thanks! I will be sending new patch-set to #42958. I will let you know,
once I am done. It would be great if you could review and merge them to
core-updates or master.
Regards,
RG.
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 236 bytes --]
next prev parent reply other threads:[~2021-03-11 9:18 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-11 3:19 GNOME 3.34 in GNU Guix and security Léo Le Bouter
2021-03-11 8:08 ` Ricardo Wurmus
2021-03-11 8:23 ` Raghav Gururajan
2021-03-11 9:11 ` Ricardo Wurmus
2021-03-11 9:17 ` Raghav Gururajan [this message]
2021-03-18 21:32 ` Danny Milosavljevic
2021-03-19 0:10 ` Ricardo Wurmus
2021-03-19 9:13 ` Guillaume Le Vaillant
2021-03-11 8:24 ` Jonathan Brielmaier
2021-03-11 8:18 ` Mark H Weaver
2021-03-11 8:28 ` Léo Le Bouter
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=2cd5f69e-9ace-a5c5-ab69-e2e560fc2953@raghavgururajan.name \
--to=rg@raghavgururajan.name \
--cc=dannym@scratchpost.org \
--cc=guix-devel@gnu.org \
--cc=lle-bout@zaclys.net \
--cc=rekado@elephly.net \
/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.