From: Csepp <raingloom@riseup.net>
To: Guix Devel <guix-devel@gnu.org>
Subject: unacknowledged patches
Date: Mon, 09 Jan 2023 13:35:08 +0100 [thread overview]
Message-ID: <86a62ropeg.fsf@riseup.net> (raw)
(asking this here as well, in addition to IRC)
Hey, I sent a large patch set last night (39 patches) but only recieved
confirmation for 13 of them. What do I need to do to get the rest
acknowledged?
Here are the ones that made it to debbugs:
https://debbugs.gnu.org/cgi/pkgreport.cgi?package=guix-patches;include=originator%3Acsepp
It's part of my thesis project for getting MirageOS unikernels deployed
with Guix, so it would help if they were accepted sooner rather than
later.
Either way I'll be adding more code during January, so it's not a
showstopper if it's not merged, but I'd rather be upstreaming things
early, so I don't have to rework huge chunks of it later.
next reply other threads:[~2023-01-09 12:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 12:35 Csepp [this message]
2023-01-09 15:01 ` unacknowledged patches Csepp
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=86a62ropeg.fsf@riseup.net \
--to=raingloom@riseup.net \
--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).