On Mon, Apr 25, 2016 at 2:14 AM, Duy Nguyen <pclouds@xxxxxxxxx> wrote: > On Mon, Apr 25, 2016 at 12:42 AM, Ramsay Jones > <ramsay@xxxxxxxxxxxxxxxxxxxx> wrote: >> >> >> On 24/04/16 17:56, Christian Couder wrote: >>> On Sun, Apr 24, 2016 at 6:27 PM, Christian Couder >>> <christian.couder@xxxxxxxxx> wrote: >>>> On Sun, Apr 24, 2016 at 5:23 PM, Ramsay Jones >>>> <ramsay@xxxxxxxxxxxxxxxxxxxx> wrote: >>>>> >>>>> 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@xxxxxxxxxxxxx. > > #78 moves 4000k lines around and ends up ~260k in size, I think it may > have hit vger limit. Yeah probably. Thanks for looking at this. I think I will have to split it into smaller patches in a v2. >>> 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). Thanks for checking. -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html