From: Josselin Poiret via Bug reports for GNU Guix <bug-guix@gnu.org>
To: Skyler <skyvine@protonmail.com>
Cc: 62448@debbugs.gnu.org
Subject: bug#62448: [PATCH] doc: Note that `guix shell` should contain base language packages.
Date: Wed, 12 Apr 2023 10:35:54 +0200 [thread overview]
Message-ID: <87cz49v6ol.fsf@jpoiret.xyz> (raw)
In-Reply-To: <LlwwxNps9NeeEH17HGch8TshLxZe0zFYbC9_27tDUs62l17Z7_xVB1nngBHU1ZhnxchS1B_grI5KItWfA2d3QtiP974mawbrkXo7alfiLg4=@protonmail.com>
[-- Attachment #1: Type: text/plain, Size: 465 bytes --]
Hi Skyler,
Skyler <skyvine@protonmail.com> writes:
> Is there a normal timeline for patch review or is it mor of an "as resources allow" type of deal?
Unfortunately no, there are no guarantees: someone needs to take some
time to look at this, and we can't force anyone to do it. The fact that
it's in a bug report instead of a patch submission probably doesn't
help, let me see if I can fix this with a debbugs command.
Best,
--
Josselin Poiret
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 682 bytes --]
next prev parent reply other threads:[~2023-04-12 8:37 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-25 19:10 bug#62448: Inconsistent guile enviornment from guix shell Skyler via Bug reports for GNU Guix
2023-03-29 21:23 ` Skyler via Bug reports for GNU Guix
2023-03-30 20:24 ` Josselin Poiret via Bug reports for GNU Guix
2023-03-30 20:42 ` bug#62448: [PATCH] doc: Note that `guix shell` should contain base language packages Josselin Poiret via Bug reports for GNU Guix
2023-04-11 22:57 ` Skyler via Bug reports for GNU Guix
2023-04-12 8:35 ` Josselin Poiret via Bug reports for GNU Guix [this message]
2023-04-12 12:43 ` Maxim Cournoyer
2023-04-13 19:53 ` Skyler via Bug reports for GNU Guix
2023-04-12 11:07 ` Simon Tournier
2023-08-25 16:30 ` Josselin Poiret via Bug reports for GNU Guix
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=87cz49v6ol.fsf@jpoiret.xyz \
--to=bug-guix@gnu.org \
--cc=62448@debbugs.gnu.org \
--cc=dev@jpoiret.xyz \
--cc=skyvine@protonmail.com \
/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).