From mboxrd@z Thu Jan  1 00:00:00 1970
From: Ricardo Wurmus <ricardo.wurmus@mdc-berlin.de>
Subject: Re: Patch tracking
Date: Mon, 2 May 2016 10:25:51 +0200
Message-ID: <idjoa8o6f3k.fsf@bimsb-sys02.mdc-berlin.net>
References: <87h9g0eq1c.fsf@grrlz.net> <87d1qogcfw.fsf@grrlz.net>
	<idjvb4fsyru.fsf@bimsb-sys02.mdc-berlin.net>
	<87h9fz7pe0.fsf@gnu.org> <8737qlhkm6.fsf@gnu.org>
	<87lh3ykunc.fsf_-_@gnu.org> <5721F440.5080204@gmail.com>
	<87twimgc77.fsf@gnu.org>
Mime-Version: 1.0
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Return-path: <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
Received: from eggs.gnu.org ([2001:4830:134:3::10]:43894)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <Ricardo.Wurmus@mdc-berlin.de>) id 1ax9Bn-0006z2-PW
	for guix-devel@gnu.org; Mon, 02 May 2016 04:26:54 -0400
Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <Ricardo.Wurmus@mdc-berlin.de>) id 1ax9Bb-0006AN-ON
	for guix-devel@gnu.org; Mon, 02 May 2016 04:26:42 -0400
In-Reply-To: <87twimgc77.fsf@gnu.org>
List-Id: "Development of GNU Guix and the GNU System distribution."
	<guix-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/guix-devel/>
List-Post: <mailto:guix-devel@gnu.org>
List-Help: <mailto:guix-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/guix-devel>,
	<mailto:guix-devel-request@gnu.org?subject=subscribe>
Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org
Sender: "Guix-devel" <guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org>
To: Ludovic =?utf-8?Q?Court=C3=A8s?= <ludo@gnu.org>
Cc: guix-devel@gnu.org, Ben Woodcroft <woodibe@gmail.com>


Ludovic Court=C3=A8s <ludo@gnu.org> writes:

> Ben Woodcroft <woodibe@gmail.com> skribis:
>
>> On 28/04/16 18:24, Ludovic Court=C3=A8s wrote:
>>> ludo@gnu.org (Ludovic Court=C3=A8s) skribis:
>>>
>>>> As an experiment (it may disappear anytime), I generated the
>>>> =E2=80=98patches.json=E2=80=99 file for =E2=80=9Cpatches=E2=80=9D, s=
o you can now run:
>>>>
>>>>    guix package -i patches
>>>>    patches fetch https://mirror.hydra.gnu.org/patches/patches.json
>>>>    patches list status:committed
>>> Please try!  :-)
>>
>> I quite like the concept and it was easy to get started, but I didn't
>> have a lot of success applying patches - I tried one from Rob, Ricardo
>> and Manolis. Rob's patch was malformed, while Ricardo's and Manolis'
>> was empty.
>>
>> e.g.
>>
>> $ patches apply id:87h9emxnk5.fsf@elephly.net
>> Patch is empty. Was it split wrong?
>> When you have resolved this problem, run "git am --continue".
>> If you prefer to skip this patch, run "git am --skip" instead.
>> To restore the original branch and stop patching, run "git am --abort"=
.
>>
>> I'm running that version of patches that you just pushed Ludo. Have
>> you had a similar experience?
>
> Yeah, I think the tool assumes that patches appear right in the message
> body, as with =E2=80=98git send-email=E2=80=99, but some of us send pat=
ches as
> attachments (I know Ricardo does).
>
> If we choose to use the tool, we may have to bend our practices a littl=
e
> bit to placate it.

Okay, I=E2=80=99ll send patches inline in the future.  I think I set up g=
it
send-mail a while ago, but I=E2=80=99m not yet in the habit of using it
consistently.  I=E2=80=99ll try!

~~ Ricardo