From: Greg Hogan <code@greghogan.com>
To: Zhu Zihao <all_but_last@163.com>
Cc: 55001@debbugs.gnu.org
Subject: [bug#55001] gnu: git: Update to 2.36.0 [fixes CVE-2022-24765] Was: Acknowledgement ([PATCH] gnu: git: Update to 2.35.2 [fixes CVE-2022-24765].)
Date: Tue, 19 Apr 2022 10:08:16 -0400 [thread overview]
Message-ID: <CA+3U0Z=V_uxi8JtxhqZjjWBKD-m-2CiZ5AhGvM7iY5zYck_N8Q@mail.gmail.com> (raw)
In-Reply-To: <86mtgh77k2.fsf@163.com>
[-- Attachment #1: Type: text/plain, Size: 555 bytes --]
This update built successfully for me, and also all dependent packages with
'git' in the name:
./pre-inst-env guix refresh -l git | cut -d: -f2- | tr ' ' '\n' | grep git |
xargs ./pre-inst-env guix build
On Tue, Apr 19, 2022 at 5:21 AM Zhu Zihao <all_but_last@163.com> wrote:
>
> Greg Hogan <code@greghogan.com> writes:
>
> > And now git 2.36 has been released.
>
> A new patch that updates to 2.36 is uploaded. Thanks for your mention :)
>
>
> --
> Retrieve my PGP public key:
>
> gpg --recv-keys D47A9C8B2AE3905B563D9135BE42B352A9F6821F
>
> Zihao
>
[-- Attachment #2: Type: text/html, Size: 1088 bytes --]
next prev parent reply other threads:[~2022-04-19 14:11 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-18 13:42 [bug#55001] [PATCH] gnu: git: Update to 2.35.2 [fixes CVE-2022-24765] Zhu Zihao
[not found] ` <handler.55001.B.165028941728102.ack@debbugs.gnu.org>
2022-04-18 14:23 ` [bug#55001] Acknowledgement ([PATCH] gnu: git: Update to 2.35.2 [fixes CVE-2022-24765].) Zhu Zihao
2022-04-18 17:33 ` Greg Hogan
2022-04-19 9:19 ` [bug#55001] gnu: git: Update to 2.36.0 [fixes CVE-2022-24765] Was: " Zhu Zihao
2022-04-19 14:08 ` Greg Hogan [this message]
2022-04-23 4:20 ` Zhu Zihao
2022-04-27 9:33 ` bug#55001: [PATCH] gnu: git: Update to 2.35.2 [fixes CVE-2022-24765] Mathieu Othacehe
2022-04-18 15:53 ` [bug#55001] " Greg Hogan
2022-04-18 16:02 ` Zhu Zihao
2022-04-18 18:03 ` Maxime Devos
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='CA+3U0Z=V_uxi8JtxhqZjjWBKD-m-2CiZ5AhGvM7iY5zYck_N8Q@mail.gmail.com' \
--to=code@greghogan.com \
--cc=55001@debbugs.gnu.org \
--cc=all_but_last@163.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 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.