From: Vincent Legoll <vincent.legoll@gmail.com>
To: Leo Famulari <leo@famulari.name>
Cc: 41533@debbugs.gnu.org
Subject: [bug#41533] [PATCH 0/10] Misc updates
Date: Tue, 26 May 2020 20:11:54 +0200 [thread overview]
Message-ID: <9329bc93-c4d6-b3df-2acf-51ad26f8d510@gmail.com> (raw)
In-Reply-To: <20200526175609.GD25821@jasmine.lan>
On 26/05/2020 19:56, Leo Famulari wrote:
> In general, it's hard to decide what to do with this bug ticket, since
> some of the patches can't be pushed to master. Should we close it? Leave
> it open? I think the best move is to split the patches into their own
> bug ticket.
All the patches are independent, I just did them all in a series to
minimize the email churn.
I was thinking committer(s) would cherry-pick the ready ones (all but
haproxy (already done by Tobias), netpbm & mupdf).
Just tell me what you prefer.
--
Vincent Legoll
prev parent reply other threads:[~2020-05-26 18:13 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 21:56 [bug#41533] [PATCH 0/10] Misc updates Vincent Legoll
2020-05-25 21:57 ` [bug#41533] [PATCH 01/10] gnu: ansible: Update to 2.9.9 Vincent Legoll
2020-05-25 21:57 ` [bug#41533] [PATCH 02/10] gnu: ffmpeg: Update to 4.2.3 Vincent Legoll
2020-05-26 17:54 ` Leo Famulari
2020-05-25 21:57 ` [bug#41533] [PATCH 03/10] gnu: unbound: Update to 1.10.1 Vincent Legoll
2020-05-25 21:57 ` [bug#41533] [PATCH 04/10] gnu: haproxy: Update to 2.1.4 Vincent Legoll
2020-05-25 21:57 ` [bug#41533] [PATCH 05/10] gnu: gitolite: Update to 3.6.11 Vincent Legoll
2020-05-25 21:57 ` [bug#41533] [PATCH 06/10] gnu: nagios: Update to 4.4.6 Vincent Legoll
2020-05-25 21:57 ` [bug#41533] [PATCH 07/10] gnu: mupdf: Update to 1.17.0 Vincent Legoll
2020-05-26 7:16 ` Efraim Flashner
2020-05-25 21:57 ` [bug#41533] [PATCH 08/10] gnu: xerces-c: Update to 3.2.3 Vincent Legoll
2020-05-25 21:57 ` [bug#41533] [PATCH 09/10] gnu: java-xerces: Update to 2.12.1 Vincent Legoll
2020-05-25 21:58 ` [bug#41533] [PATCH 10/10] gnu: netpbm: Update to 10.90.2 Vincent Legoll
[not found] ` <handler.41533.B.1590443793302.ack@debbugs.gnu.org>
2020-05-25 22:04 ` [bug#41533] Acknowledgement ([PATCH 0/10] Misc updates) Vincent Legoll
2020-05-25 22:45 ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-25 23:01 ` Vincent Legoll
2020-05-27 2:02 ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-27 16:50 ` Vincent Legoll
2020-05-27 17:16 ` Leo Famulari
2020-05-27 17:24 ` Tobias Geerinckx-Rice via Guix-patches via
2020-05-27 20:02 ` bug#41533: " Vincent Legoll
2020-05-26 17:56 ` [bug#41533] [PATCH 0/10] Misc updates Leo Famulari
2020-05-26 18:11 ` Vincent Legoll [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
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=9329bc93-c4d6-b3df-2acf-51ad26f8d510@gmail.com \
--to=vincent.legoll@gmail.com \
--cc=41533@debbugs.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).