From: ludo@gnu.org (Ludovic Courtès)
To: Leo Famulari <leo@famulari.name>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>, rain1@openmailbox.org
Subject: Re: pcmanfm version update
Date: Wed, 13 Apr 2016 23:31:02 +0200 [thread overview]
Message-ID: <878u0hci21.fsf@gnu.org> (raw)
In-Reply-To: <20160410010619.GB29029@jasmine> (Leo Famulari's message of "Sat, 9 Apr 2016 21:06:19 -0400")
Leo Famulari <leo@famulari.name> skribis:
> On Sat, Apr 09, 2016 at 10:59:03PM +0300, Efraim Flashner wrote:
>> We do have some packages that have to be updated together, acme and
>> letsencrypt, python-cryptography and python-cryptography-vectors. But
>> those do have a commit message that they are updated together.
>
> If those packages were updated separately, the build would break after
> the first commit. Neither of those package pairs works if the versions
> are not in sync [0].
>
> In my opinion, that is a valid reason for updating multiple packages in
> the same commit.
If that is the case (I wouldn’t be surprised), I agree it’s a valid
reason.
Anyway, it’s no big deal, so we shouldn’t block otherwise
uncontroversial and non-disrupting patches for 1 week just because of
this IMO.
Thoughts? Someone applies it? :-)
Ludo’.
next prev parent reply other threads:[~2016-04-13 21:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-04 20:22 mplayer version update rain1
2016-04-04 20:34 ` Mark H Weaver
2016-04-07 20:12 ` pcmanfm " rain1
2016-04-09 8:47 ` Alex Kost
[not found] ` <71ca60a5ce463ec85842355bdf5d86c6@openmailbox.org>
2016-04-09 16:37 ` Alex Kost
2016-04-09 17:19 ` Andreas Enge
2016-04-09 19:59 ` Efraim Flashner
2016-04-09 20:10 ` Mathieu Lirzin
2016-04-10 1:06 ` Leo Famulari
2016-04-13 21:31 ` Ludovic Courtès [this message]
2016-04-14 0:49 ` Leo Famulari
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=878u0hci21.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=alezost@gmail.com \
--cc=guix-devel@gnu.org \
--cc=leo@famulari.name \
--cc=rain1@openmailbox.org \
/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).