From: Tomas Volf <~@wolfsden.cz>
To: Z572 <zhengjunjie@iscas.ac.cn>
Cc: 74464-done@debbugs.gnu.org
Subject: [bug#74464] [PATCH] gnu: buildah: Update to 1.38.0.
Date: Sun, 24 Nov 2024 15:55:06 +0100 [thread overview]
Message-ID: <87h67wfzqt.fsf@wolfsden.cz> (raw)
In-Reply-To: <87ed315t9l.fsf@iscas.ac.cn> (zhengjunjie@iscas.ac.cn's message of "Sun, 24 Nov 2024 09:12:54 +0800")
[-- Attachment #1: Type: text/plain, Size: 1004 bytes --]
Hi,
thank you for merging my patches. I just have a question regarding the
following:
Z572 <zhengjunjie@iscas.ac.cn> writes:
> Tomas Volf <~@wolfsden.cz> writes:
>
>> * gnu/packages/containers.scm (buildah): Update to 1.38.0.
>> <native-inputs>: Use go-1.22.
>
> [native-inputs]: Use go-1.22.
I tried following the `(standards)Indicating the Part Changed' manual,
since Guix claims to follow the Change log format but I did not manage
to find its own documentation for it. According to the info manual, the
`[..]' should be used for conditional changes (which this is not). The
`<..>' should be used to indicate part changed (which this is).
Could you please point me to a documentation where I could read more on
what Guix's deviations from the GNU Change Logs format are so that I can
adhere to it next time?
Thank you and have a nice day,
Tomas
--
There are only two hard things in Computer Science:
cache invalidation, naming things and off-by-one errors.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 853 bytes --]
next prev parent reply other threads:[~2024-11-24 14:56 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-21 14:08 [bug#74464] [PATCH] gnu: buildah: Update to 1.38.0 Tomas Volf
2024-11-23 21:24 ` [bug#74464] QA review for 74464 Aaron Covrig via Guix-patches via
2024-11-24 1:12 ` bug#74464: [PATCH] gnu: buildah: Update to 1.38.0 Z572
2024-11-24 14:55 ` Tomas Volf [this message]
2024-11-24 16:03 ` [bug#74464] " Zheng Junjie
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=87h67wfzqt.fsf@wolfsden.cz \
--to=~@wolfsden.cz \
--cc=74464-done@debbugs.gnu.org \
--cc=zhengjunjie@iscas.ac.cn \
/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).