Hello,
thanks for bringing up the question!
Am Thu, Jun 27, 2024 at 07:04:49PM -0400 schrieb Richard Sent:
> Meanwhile in Guix commit messages, [foo] seems to be used to refer to a
> subset of a larger part [2]:
> From what I'm seeing, the GNU Changelog convention is to indicate
> subsets using <
Hi Maya, Ludo' and Attila,
On Thu, Jun 27 2024, Maya wrote:
> I still don't know how to fix the issue properly, but at least I can
> reconfigure my system now <3
I have a reproducer! In the code below, please change "sunday" to "0",
together with this line in your "services":
(service mda
On Fri, Jun 28 2024, Felix Lechner wrote:
> even the Magic SysRq key 'i' [...] enough will not stop it.
Sorry, I meant to write 'e' which presumably refers to SIGTERM rather
than SIGKILL.
Hey y'all,
I've avoided weighing in on this topic because I'm of two minds about
it. Still, when members of the community raise concerns, it's important
to take those concerns seriously. We must be careful how we address
them because the opinions and concerns of any community member are as
le
Hi Ludo'
On Thu, Jun 27 2024, Ludovic Courtès wrote:
> I like resolution of bug numbers and commit IDs, but I find that
> echoing the title of HTML pages is often redundant and unnecessary.
Following the cue from Andreas [1] I disabled the generic HTML
titles. [2] That ought to address the gener
Hi Richard,
Richard Sent writes:
> Hi Guix,
>
> I noticed that there seems to be discrepencies between the GNU Changelog
> format and Guix's commit message convention. For example, see these
> lines from [1].
>
>>Our convention for indicating conditional changes is to use _square
>> brackets
Hi Maxim,
Thanks for the detailed response! (And Andreas as well)
> Another Emacs tip for those who don't know it yet: pressing 'C'
> (capital C) on a diff hunk while authoring a commit message using
> Magit will create some ChangeLog entry stub in the commit message
> buffer, which saves a lot o
Hi Guix,
Am Freitag, dem 28.06.2024 um 21:11 -0400 schrieb Maxim Cournoyer:
> Richard Sent writes:
>
> > Another one seems to be the [security fixes], [fixes CVE-...], and
> > [fixes TROVE-...] blocks added to certain header lines. What other
> > tags exist? There seems to be inconsistency here
