From: "Ludovic Courtès" <ludo@gnu.org>
To: Bruno Victal <mirai@makinata.eu>
Cc: Liliana Marie Prikler <liliana.prikler@gmail.com>,
66500-done@debbugs.gnu.org
Subject: bug#66500: [PATCH core-updates v2 0/3] Custom output labels for copy-build-system.
Date: Wed, 20 Dec 2023 22:10:35 +0100 [thread overview]
Message-ID: <874jgch96c.fsf@gnu.org> (raw)
In-Reply-To: <cover.1697729341.git.mirai@makinata.eu> (Bruno Victal's message of "Thu, 19 Oct 2023 16:37:26 +0100")
Hi Bruno,
Bruno Victal <mirai@makinata.eu> skribis:
> build: copy-build-system: Allow specifying different output labels.
> gnu: docbook-dsssl: Refactor install-plan.
> gnu: docbook-dsssl: Fix script installation path.
Applied, thanks!
Ludo’.
prev parent reply other threads:[~2023-12-20 21:11 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-12 15:27 [bug#66500] [PATCH core-updates 0/3] Custom output labels for copy-build-system Bruno Victal
2023-10-12 15:30 ` [bug#66500] [PATCH core-updates 1/3] build: copy-build-system: Allow specifying different output labels Bruno Victal
2023-10-19 9:46 ` Liliana Marie Prikler
2023-10-19 15:36 ` Bruno Victal
2023-10-12 15:30 ` [bug#66500] [PATCH core-updates 2/3] gnu: docbook-dsssl: Refactor install-plan Bruno Victal
2023-10-19 9:47 ` Liliana Marie Prikler
2023-10-19 15:25 ` Bruno Victal
2023-10-12 15:30 ` [bug#66500] [PATCH core-updates 3/3] gnu: docbook-dsssl: Fix script installation path Bruno Victal
2023-10-19 15:37 ` [bug#66500] [PATCH core-updates v2 0/3] Custom output labels for copy-build-system Bruno Victal
2023-10-19 15:38 ` [bug#66500] [PATCH core-updates v2 1/3] build: copy-build-system: Allow specifying different output labels Bruno Victal
2023-10-19 15:38 ` [bug#66500] [PATCH core-updates v2 2/3] gnu: docbook-dsssl: Refactor install-plan Bruno Victal
2023-10-19 15:38 ` [bug#66500] [PATCH core-updates v2 3/3] gnu: docbook-dsssl: Fix script installation path Bruno Victal
2023-12-20 21:10 ` Ludovic Courtès [this message]
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=874jgch96c.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=66500-done@debbugs.gnu.org \
--cc=liliana.prikler@gmail.com \
--cc=mirai@makinata.eu \
/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.