all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Josselin Poiret via Guix-patches via <guix-patches@gnu.org>
To: Leo Famulari <leo@famulari.name>, Kaelyn <kaelyn.alexi@protonmail.com>
Cc: 52562@debbugs.gnu.org
Subject: [bug#52562] [PATCH] gnu: xorg-server: Update to 21.1.2.
Date: Wed, 22 Dec 2021 14:56:19 +0100	[thread overview]
Message-ID: <875yrgg2v0.fsf@jpoiret.xyz> (raw)
In-Reply-To: <YcIQp5rRrA0MBM04@jasmine.lan>

Hello,

Leo Famulari <leo@famulari.name> writes:
> In case anybody is wondering about the security issues, the commit
> message has been amended like this in my tree:
>
> ------
> gnu: xorg-server: Update to 21.1.2 [fixes CVE-2021-{4008,4009,4010,4011}].
>
> * gnu/packages/xorg.scm (xorg-server): Update to 21.1.2.
> (xorg-server-for-tests): Use version 21.1.1.
> ------

Just pitching in to say that those CVE numbers should be fully typed
instead of using shell expansion-style, so that one can run `git log
--grep=CVE-2021-4008`.  Note that these can be in the commit message
body.

-- 
Josselin Poiret




  parent reply	other threads:[~2021-12-22 14:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-16 23:29 [bug#52562] [PATCH] gnu: xorg-server: Update to 21.1.2 Kaelyn Takata via Guix-patches via
2021-12-18 15:23 ` Kaelyn via Guix-patches via
2021-12-18 20:40 ` Leo Famulari
2021-12-19  1:49   ` Kaelyn via Guix-patches via
2021-12-19  4:56     ` Leo Famulari
2021-12-19 20:30       ` Leo Famulari
2021-12-21 17:36         ` Leo Famulari
2021-12-21 17:47           ` Leo Famulari
2021-12-21 19:09             ` Leo Famulari
2021-12-22 13:56           ` Josselin Poiret via Guix-patches via [this message]
2021-12-22 17:19             ` Leo Famulari
2021-12-22 23:38           ` bug#52562: " 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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=875yrgg2v0.fsf@jpoiret.xyz \
    --to=guix-patches@gnu.org \
    --cc=52562@debbugs.gnu.org \
    --cc=dev@jpoiret.xyz \
    --cc=kaelyn.alexi@protonmail.com \
    --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 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.