From: Simon Tournier <zimon.toutoune@gmail.com>
To: "Tobias Geerinckx-Rice" <me@tobias.gr>,
"Maxim Cournoyer" <maxim.cournoyer@gmail.com>,
"André Batista" <nandre@riseup.net>
Cc: 61246@debbugs.gnu.org
Subject: [bug#61246] [PATCH] gnu: libgit2: Update to 1.5.1.
Date: Mon, 20 Feb 2023 11:05:43 +0100 [thread overview]
Message-ID: <87y1os4poo.fsf@gmail.com> (raw)
In-Reply-To: <87h6vix2jm.fsf@nckx>
Hi,
On sam., 18 févr. 2023 at 19:13, Tobias Geerinckx-Rice via Guix-patches via <guix-patches@gnu.org> wrote:
> Tobias Geerinckx-Rice 写道：
>> I belatedly second Zimoun here:
>>
>>> This patch series should be split into 3 atomic commits.
>
> Or maybe I misinterpreted the intention.
>
> When debugging this, I would have liked to find separate commits a
> for each version, or a more generic title (without the misleading
> ‘to 1.5.1’).
The intention was: « When debugging this, I would have liked to find
separate commits a for each version, or a more generic title (without
the misleading ‘to 1.5.1’). » :-)
Just to point that as member of the Julia team, I know by experience
that the dependency relationship between Julia and the Git ecosystem can
be tedious to find. Hence my proposal to split – it helps to prevent
breakage or help to debug it.
Thanks Tobias for the quick fix!
Cheers,
simon
next prev parent reply other threads:[~2023-02-20 10:43 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-03 3:11 [bug#61246] [PATCH] gnu: libgit2: Update to 1.5.1 André Batista
2023-02-08 15:31 ` Simon Tournier
2023-02-17 19:05 ` [bug#61246] [PATCH v3 0/3] " André Batista
2023-02-17 19:06 ` [bug#61246] [PATCH v3 1/3] gnu: libgit2-1.1: Remove it André Batista
2023-02-17 19:06 ` [bug#61246] [PATCH v3 2/3] doc: Explain how to use local guix repositories André Batista
2023-02-17 19:58 ` Maxim Cournoyer
2023-02-17 23:24 ` André Batista
2023-02-18 17:35 ` Maxim Cournoyer
2023-02-22 18:10 ` André Batista
2023-02-23 21:59 ` bug#61246: " Maxim Cournoyer
2023-02-23 12:43 ` [bug#61246] " André Batista
2023-02-23 22:38 ` Maxim Cournoyer
2023-02-17 20:45 ` Maxim Cournoyer
2023-02-17 23:31 ` André Batista
2023-02-18 17:43 ` Maxim Cournoyer
2023-02-17 19:07 ` [bug#61246] [PATCH v3 3/3] gnu: libgit2: Update to 1.5.1 André Batista
2023-02-08 15:43 ` [bug#61246] [PATCH v2] " André Batista
2023-02-09 3:25 ` [bug#61246] [PATCH] " Maxim Cournoyer
2023-02-09 12:30 ` zimoun
2023-02-10 17:53 ` André Batista
2023-02-17 19:15 ` André Batista
2023-02-17 19:23 ` André Batista
2023-02-17 19:46 ` Maxim Cournoyer
2023-02-17 23:33 ` André Batista
2023-02-18 18:04 ` Tobias Geerinckx-Rice via Guix-patches via
2023-02-18 18:13 ` Tobias Geerinckx-Rice via Guix-patches via
2023-02-18 20:45 ` Maxim Cournoyer
2023-02-20 10:08 ` Simon Tournier
2023-02-20 10:05 ` Simon Tournier [this message]
2023-02-22 18:17 ` André Batista
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=87y1os4poo.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=61246@debbugs.gnu.org \
--cc=maxim.cournoyer@gmail.com \
--cc=me@tobias.gr \
--cc=nandre@riseup.net \
/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.