From: "Raghav Gururajan" <raghavgururajan@disroot.org>
To: guix-devel@gnu.org
Subject: Patches
Date: Wed, 08 Jan 2020 09:38:05 +0000 [thread overview]
Message-ID: <bf2fc77825cecc03a8e291e1012ef6b7@disroot.org> (raw)
Hello Guix!
In recent days, I have sent series of patches. It appears it is confusing to know in which order these patches are to be pushed. So I have made the following list to outline the order in which they are to be committed.
[1] 38904
[2] 38905
[3] 38906
[4] 38914 (38894 --> 38896 --> 38898 --> 38901 --> 38914)
[5] 38911 (38909 --> 38911)
[6] 38931 (38930 --> 38931)
[7] 38953
[8] 38935
[9] 38954
Sorry for creating the confusion. I will do better for future patches. :-)
Regards,
RG.
reply other threads:[~2020-01-08 9:38 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=bf2fc77825cecc03a8e291e1012ef6b7@disroot.org \
--to=raghavgururajan@disroot.org \
--cc=guix-devel@gnu.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).