Re: Patch tracking

[Ludovic Courtès]

Ben Woodcroft  skribis:

> On 28/04/16 18:24, Ludovic Courtès wrote:
>> l...@gnu.org (Ludovic Courtès) skribis:
>>
>>> As an experiment (it may disappear anytime), I generated the
>>> ‘patches.json’ file for “patches”, so 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@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 ‘git send-email’, but some of us send patches as
attachments (I know Ricardo does).

If we choose to use the tool, we may have to bend our practices a little
bit to placate it.

Thanks for trying it out!

Ludo’.

Re: Patch tracking

[Ben Woodcroft]

On 28/04/16 18:24, Ludovic Courtès wrote:

l...@gnu.org (Ludovic Courtès) skribis:


As an experiment (it may disappear anytime), I generated the
‘patches.json’ file for “patches”, so 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@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?


ben

Patch tracking

[Ludovic Courtès]

l...@gnu.org (Ludovic Courtès) skribis:

> As an experiment (it may disappear anytime), I generated the
> ‘patches.json’ file for “patches”, so you can now run:
>
>   guix package -i patches
>   patches fetch https://mirror.hydra.gnu.org/patches/patches.json
>   patches list status:committed

Please try!  :-)

> The “documentation” is at:
>
>   https://github.com/aliguori/patches/blob/master/README.md
>
> The project appears to be inactive though.  :-/

Good news: development has moved to:

  https://github.com/stefanha/patches

The QEMU folks also suggested looking at “patchew”:

  https://github.com/famz/patchew

An instance for QEMU can be seen at:

  http://140.211.15.4:8383/

Currently it looks very similar to Patchwork (or “patches”).

Ludo’.