From: Maxim Cournoyer <maxim.cournoyer@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 71381-done@debbugs.gnu.org, Ashish SHUKLA <ashish.is@lostca.se>
Subject: [bug#71381] Why is this closed ?
Date: Wed, 26 Jun 2024 15:01:17 -0400 [thread overview]
Message-ID: <87le2rbkaq.fsf@gmail.com> (raw)
In-Reply-To: <Znwn4Prgc5O3rCGN@jasmine.lan> (Leo Famulari's message of "Wed, 26 Jun 2024 10:38:24 -0400")
Hi Leo,
Leo Famulari <leo@famulari.name> writes:
> On Wed, Jun 26, 2024 at 10:25:40AM -0400, Leo Famulari wrote:
>> On Mon, Jun 24, 2024 at 04:07:52AM +0000, Ashish SHUKLA via Guix-patches via wrote:
>> > I'm wondering why is this bug report closed, as I don't see any commit
>> > to git derivation in the master branch atm.
>>
>> This patched was pushed to master as commit 26c0ff98cf4302fc69539272d646c0ef28991991
>>
>> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=26c0ff98cf4302fc69539272d646c0ef28991991
>>
>> Now, I see that some other change was included to
>> 'gnu/packages/linux.scm', probably by accident. I'm going to look into
>> that now.
>
> I went ahead and reverted this change to bcc, leaving the Git update in
> place.
>
> Maxim, let us know if I shouldn't have done that, and the bcc change
> should be reinstated.
Seems I had squashed the bcc change in the wrong commit while working on
a stack of patches to commit. It's still useful (as 'guix lint bcc'
would say), so I've reinstated that in its own commit and the git update
too:
03459ca165 master gnu: git: Update to 2.45.2.
a3b8a9627b gnu: bcc: Add bash-minimal to inputs.
Thanks for the heads-up.
--
Maxim
next prev parent reply other threads:[~2024-06-26 19:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 14:30 [bug#71381] [PATCH] gnu: git: Update to 2.45.2 ashish.is--- via Guix-patches via
2024-06-24 4:07 ` [bug#71381] Why is this closed ? Ashish SHUKLA via Guix-patches via
2024-06-26 14:25 ` Leo Famulari
2024-06-26 14:38 ` Leo Famulari
2024-06-26 19:01 ` Maxim Cournoyer [this message]
2024-06-26 19:21 ` Leo Famulari
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=87le2rbkaq.fsf@gmail.com \
--to=maxim.cournoyer@gmail.com \
--cc=71381-done@debbugs.gnu.org \
--cc=ashish.is@lostca.se \
--cc=leo@famulari.name \
/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).