[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Codifying/Documenting Guix commit message conventions?
From: |
Liliana Marie Prikler |
Subject: |
Re: Codifying/Documenting Guix commit message conventions? |
Date: |
Sun, 30 Jun 2024 08:25:35 +0200 |
User-agent: |
Evolution 3.48.4 |
Am Samstag, dem 29.06.2024 um 21:11 -0400 schrieb Maxim Cournoyer:
> Hi Liliana,
>
> Liliana Marie Prikler <liliana.prikler@gmail.com> writes:
> > I think we should use a "Fixes: [short description] <URI>" footer
> > for both Guix and upstream bugs, that can easily be parsed –
> > hopefully by both humans and machines. That would give the
> > interested reader the (contextual) information they need, while
> > also leaving the main body to a more thorough description of the
> > patch itself.
>
> That's a good idea, and I already use a "Fixes:" git trailer for
> fixed bugs, but I also like to be able to see from the 'git log'
> output which commits were security related (I see value in the
> summary [security fixes] "tag").
Oh, sure, my preference w.r.t. that would be to have [security fix] or
[security fixes] in the header, and the particular CVEs in the trailer.
Cheers