From: Alex Kost <alezost@gmail.com>
To: rain1@openmailbox.org
Cc: guix-devel@gnu.org
Subject: Re: pcmanfm version update
Date: Sat, 09 Apr 2016 19:37:13 +0300 [thread overview]
Message-ID: <87bn5i4u2u.fsf@gmail.com> (raw)
In-Reply-To: <71ca60a5ce463ec85842355bdf5d86c6@openmailbox.org> (rain1@openmailbox.org's message of "Sat, 09 Apr 2016 12:43:57 +0000")
Please keep guix-devel Cc-ed!
rain1@openmailbox.org (2016-04-09 15:43 +0300) wrote:
> On 2016-04-09 08:47, Alex Kost wrote:
>> rain1@openmailbox.org (2016-04-07 23:12 +0300) wrote:
>>
>>> pcmanfm (and its library libfm) were at version 1.2.3 from 2 years
>>> ago. This patch updates them to 1.2.4, the most recent version from
>>> February.
>>
>>> From 437fee1d56001da92b5b9cd65811d65b1316aec2 Mon Sep 17 00:00:00 2001
>>> From: Raymond Nicholson <rain1@openmailbox.org>
>>> Date: Thu, 7 Apr 2016 21:07:59 +0100
>>> Subject: [PATCH] gnu: pcmanfm: Update to 1.2.4.
>>>
>>> * gnu/packages/lxde.scm (pcmanfm): Update to 1.2.4.
>>> * gnu/packages/lxde.scm (libfm): Update to 1.2.4.
>>> ---
>>> gnu/packages/lxde.scm | 8 ++++----
>>> 1 file changed, 4 insertions(+), 4 deletions(-)
>>
>> Since these are 2 updates, could you send 2 patches for each package?
>> Thanks!
>>
> I don't think that makes sense, libfm is part of pcmanfm.
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.
--
Alex
next prev parent reply other threads:[~2016-04-09 16:37 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 [this message]
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
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=87bn5i4u2u.fsf@gmail.com \
--to=alezost@gmail.com \
--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 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).