Re: [PATCH 00/83] libify apply and use lib in am
- From
Duy Nguyen <pclouds@gmail.com>
- Date
- Apr 25, 2016, 00:14 UTC
- Message-ID
- <CACsJy8Bu+fsWP-dmckbSCRvonpqtCyvwGZWHCvjtfSWKY3A6QQ@mail.gmail.com>
- In-Reply-To
- <571D059B.2010908@ramsayjones.plus.com>
On Mon, Apr 25, 2016 at 12:42 AM, Ramsay Jones <ramsay@ramsayjones.plus.com> wrote:
Show 21 quoted lines
> > > On 24/04/16 17:56, Christian Couder wrote: >> On Sun, Apr 24, 2016 at 6:27 PM, Christian Couder >> <christian.couder@gmail.com> wrote: >>> On Sun, Apr 24, 2016 at 5:23 PM, Ramsay Jones >>> <ramsay@ramsayjones.plus.com> wrote: >>>> >>>> >>>> On 24/04/16 14:33, Christian Couder wrote: >>>>> This is a patch series about libifying `git apply` functionality, and >>>>> using this libified functionality in `git am`, so that no 'git apply' >>>>> process is spawn anymore. This makes `git am` significantly faster, so >>>>> `git rebase`, when it uses the am backend, is also significantly >>>>> faster. >>>> >>>> I just tried to git-am these patches, but patch #78 did not make it >>>> to the list. >>> >>> That's strange because gmail tells me it has been sent, and it made it >>> to chriscool@tuxfamily.org.
#78 moves 4000k lines around and ends up ~260k in size, I think it may have hit vger limit.
Show 10 quoted lines
>> Instead of waiting for the patch to appear on the list, you might want >> to use branch libify-apply-use-in-am25 in my GitHub repo: >> >> https://github.com/chriscool/git/commits/libify-apply-use-in-am25 > > Hmm, that branch doesn't correspond directly to the patches you sent > out (there are 86 commits, some marked with draft. I think commit d13d2ac > corresponds kinda to patch #83, but .... ). > > I think I'll wait to see the patches as you intend them to be seen. ;-)
I git-am'd the series then compared with the rebased version of libify-apply-use-in-am25 on master. 33198a1 (i.e. libify-apply-use-in-am25^) matches what was sent in content (didn't compare commit messages).
-- Duy