#253 feature: Fork from a patch

Opened by lthms, on April 27, 2018
lthms commented on April 27, 2018

With this patch, you can create a new branch which contains the minimal set of patches required by the patch given in arguments of fork --patch.

Do not merge, this is a work in progress

Currently, the current branch does not change after pijul fork has succeed. Unfortunately, pijul checkout fails, saying the environment is not big enough, when I try with the pijul-0.10 tag.

lthms commented on April 27, 2018

If I try to fork from the initial commit of pijul, then checkout on the newly created branch, it works like a charm.

lthms commented on April 28, 2018

If I do enough pijul diff, then I can pijul checkout. Nice protip :*.

lthms commented on May 1, 2018

Okay, so I would like to apply these patches to master in the following days.

I will try to write some tests before, but I’d love to have some feedback about the code itself. I’ve tested on my laptop, and it works like a charm.

lthms commented on May 1, 2018

Okay, everything is ready for applying to master now :).

lthms commented on May 3, 2018

I had to merge my changes with your partial checkout patch. I have pushed everything to the branch master, so don't forget to pull them before pushing again, in order to prevent conflicts on pijul upstream.

I think I will release a pijul-0.11-rc2 with “forking from a patch” this week-end, then a pijul-0.11-rc3 with “partial checkout” the week after (or whenever it’s ready, really).

After this third RC, and once stabilized, I think we will have everything we need to release pijul-0.11.0!

lthms closed this issue on May 3, 2018