From: Mathieu Lirzin <mthl@gnu.org>
To: Efraim Flashner <efraim@flashner.co.il>
Cc: guix-devel@gnu.org, Alex Kost <alezost@gmail.com>, rain1@openmailbox.org
Subject: Re: pcmanfm version update
Date: Sat, 09 Apr 2016 22:10:36 +0200 [thread overview]
Message-ID: <8737qu8rwj.fsf@gnu.org> (raw)
In-Reply-To: <20160409195903.GC7587@debian-netbook> (Efraim Flashner's message of "Sat, 9 Apr 2016 22:59:03 +0300")
Efraim Flashner <efraim@flashner.co.il> writes:
> On Sat, Apr 09, 2016 at 07:19:58PM +0200, Andreas Enge wrote:
>> On Sat, Apr 09, 2016 at 07:37:13PM +0300, Alex Kost wrote:
>> > But these are 2 different packages from 2 different sources, so I still
>> > think it makes sense to update them in 2 commits. I hope other people
>> > tell what is preferable here on their opinions, thanks.
>>
>> Yes, we always work on one package at a time.
>>
>> Andreas
>>
>
> 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.
>
> Does either libfm or pcmanfm build independant of the other being
> upgraded?
They are independent.
--
Mathieu Lirzin
next prev parent reply other threads:[~2016-04-09 20:10 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 [this message]
2016-04-10 1:06 ` Leo Famulari
2016-04-13 21:31 ` Ludovic Courtès
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8737qu8rwj.fsf@gnu.org \
--to=mthl@gnu.org \
--cc=alezost@gmail.com \
--cc=efraim@flashner.co.il \
--cc=guix-devel@gnu.org \
--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 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.