From: Michael Rohleder <mike@rohleder.de>
To: Jonathan Brielmaier <jonathan.brielmaier@web.de>
Cc: 45405@debbugs.gnu.org
Subject: [bug#45405] [PATCH] gnu: Update Xfce base to 4.16.0.
Date: Fri, 25 Dec 2020 12:43:04 +0100 [thread overview]
Message-ID: <874kkayuuv.fsf@rohleder.de> (raw)
In-Reply-To: <ec61aff4-f1bf-1982-d801-7018a6a8d38c@web.de> (Jonathan Brielmaier's message of "Fri, 25 Dec 2020 12:02:47 +0100")
[-- Attachment #1: Type: text/plain, Size: 1051 bytes --]
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?
For the commit messages I took the last xfce4 update (to 4.14) as an
example (commit 8549e0ca6fd68a57253471436de49b88b2d47e64).
If that is/was wrong, I apologize and rewrite them, although I'm not
entirely sure how.
--
"One basic notion underlying Usenet is that it is a cooperative."
Having been on USENET for going on ten years, I disagree with this.
The basic notion underlying USENET is the flame.
-- Chuq Von Rospach
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2020-12-25 11:44 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 [this message]
2021-01-13 15:15 ` Ludovic Courtès
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=874kkayuuv.fsf@rohleder.de \
--to=mike@rohleder.de \
--cc=45405@debbugs.gnu.org \
--cc=jonathan.brielmaier@web.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).