From: "Ludovic Courtès" <ludo@gnu.org>
To: Michael Rohleder <mike@rohleder.de>
Cc: 45405@debbugs.gnu.org
Subject: [bug#45405] [PATCH] gnu: Update Xfce base to 4.16.0.
Date: Wed, 13 Jan 2021 16:15:58 +0100 [thread overview]
Message-ID: <87im8098b5.fsf_-_@gnu.org> (raw)
In-Reply-To: <874kkayuuv.fsf@rohleder.de> (Michael Rohleder's message of "Fri, 25 Dec 2020 12:43:04 +0100")
Hi Michael,
Michael Rohleder <mike@rohleder.de> skribis:
> Jonathan Brielmaier <jonathan.brielmaier@web.de> writes:
>> Nice one! Although I find it better to have each update as a seperate
>> commit. If we stick with this big commit we can at least make the commit
>> message a bit leaner:
>>
>> * gnu/packages/xfce.scm (libxfce4util): Update to 4.16.0.
>> (xfconf): Update to 4.16.0.
>>
>> [arguments]: Remove failing custom-check phase. Disabled tests.
>> (libxfce4ui): Update to 4.16.0.
>>
>> [inputs]: Remove unneeded gtk+-2.
>> ...
>>
>
> A seperate commit for each update would not build inbetween, because of
> some (inter)dependencies (libxfce4util, etc...), no?
Probably; a single commit makes sense when updating large intertwined
stacks like this.
I think this fell through the cracks during the holidays. Should we go
ahead and apply it; are there additional changes needed?
Thanks,
Ludo’.
next prev parent reply other threads:[~2021-01-13 15:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-24 13:21 [bug#45405] [PATCH] gnu: Update Xfce base to 4.16.0 Michael Rohleder
2020-12-24 21:51 ` Leo Famulari
2020-12-25 13:24 ` Michael Rohleder
2020-12-25 11:02 ` Jonathan Brielmaier
2020-12-25 11:43 ` Michael Rohleder
2021-01-13 15:15 ` Ludovic Courtès [this message]
2021-01-13 16:02 ` Michael Rohleder
2021-01-14 16:20 ` bug#45405: " Ludovic Courtès
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=87im8098b5.fsf_-_@gnu.org \
--to=ludo@gnu.org \
--cc=45405@debbugs.gnu.org \
--cc=mike@rohleder.de \
/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).