From: Csepp <raingloom@riseup.net>
To: Csepp <raingloom@riseup.net>
Cc: guix-devel@gnu.org
Subject: Re: unacknowledged patches
Date: Mon, 09 Jan 2023 16:01:00 +0100 [thread overview]
Message-ID: <867cxvhhrc.fsf@riseup.net> (raw)
In-Reply-To: <86a62ropeg.fsf@riseup.net>
Csepp <raingloom@riseup.net> writes:
> (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.
Thanks to nckx, I managed to merge the accepted ones, but now it looks
like all (?) have been merged into
https://debbugs.gnu.org/cgi/bugreport.cgi?bug=60673
even the ones that did not get an issue number before.
So I think the mystery has been solved.
prev parent reply other threads:[~2023-01-09 15:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-09 12:35 unacknowledged patches Csepp
2023-01-09 15:01 ` Csepp [this message]
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=867cxvhhrc.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 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.