unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: Andreas Enge <andreas@enge.fr>,
	Felix Lechner <felix.lechner@lease-up.com>
Cc: Leo Famulari <leo@famulari.name>, guix-devel@gnu.org
Subject: Re: Commits and bug closing (was: something else)
Date: Fri, 07 Apr 2023 12:27:48 +0200	[thread overview]
Message-ID: <87mt3kkmvv.fsf@gmail.com> (raw)
In-Reply-To: <ZC8ZbA0SZCxrp2hr@jurong>

Hi,

On jeu., 06 avril 2023 at 21:11, Andreas Enge <andreas@enge.fr> wrote:

>> Do we have a hook that closes such bugs automatically via instructions
>> in commit messages?
>> If not, I'd be happy to look into writing such a thing. It would also
>> help to tie commits to bug reports, which can be good for research
>> after the fact.
>
> we do not as far as I know, and I agree that it would be useful to add
> a two-way link between bug reports and commits (for "real" bugs, not
> "issues" created from the patches list).
>
> I do not know if there is a general convention on how this should be done;
> supposedly it would need a bit of discussion to come to a consensus.

For example,

--8<---------------cut here---------------start------------->8---
substitute: Gracefully handle TLS termination while fetching narinfos.

Fixes <https://issues.guix.gnu.org/62476>.
--8<---------------cut here---------------end--------------->8---

or 

--8<---------------cut here---------------start------------->8---
services: mpd: Use proper records for user and group fields.

Deprecate using strings for these fields and prefer user-account
(resp. user-group) instead to avoid duplication within account-service-type.

Fixes #61570 <https://issues.guix.gnu.org/61570>.
--8<---------------cut here---------------end--------------->8---

Somehow, the current informal “convention” is to add,

    Fixes <https://issues.guix.gnu.org/12345>.

in the commit message that closes specific bug.  However, it is not
fully uniform,

--8<---------------cut here---------------start------------->8---
gnu: openjdk10: Build from hg.

* gnu/packages/java.scm (openjdk10)[source]: Use HG-DOWNLOAD.

This fixes <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=62071>
for OpenJDK 10.
--8<---------------cut here---------------end--------------->8---

or

--8<---------------cut here---------------start------------->8---
gnu: icecat: Fix Kerberos support.

Fixes <https://bugs.gnu.org/48959>.
--8<---------------cut here---------------end--------------->8---


Cheers,
simon


  reply	other threads:[~2023-04-07 10:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-05  2:48 [core-updates] It would be nice to fix libsndfile CVE-2021-3246 (arbitrary code execution via crafted WAV file) Leo Famulari
2023-04-05  3:13 ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-04-05  8:06   ` Josselin Poiret
2023-04-05  8:46   ` Andreas Enge
2023-04-05 15:54     ` Leo Famulari
2023-04-05 16:19     ` Felix Lechner via Development of GNU Guix and the GNU System distribution.
2023-04-06 19:11       ` Commits and bug closing (was: something else) Andreas Enge
2023-04-07 10:27         ` Simon Tournier [this message]
2023-04-13  2:22           ` Commits and bug closing Maxim Cournoyer

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=87mt3kkmvv.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=andreas@enge.fr \
    --cc=felix.lechner@lease-up.com \
    --cc=guix-devel@gnu.org \
    --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).