Re: [PATCH v3 00/34] libify mailinfo and call it directly from am

2015-10-26 Thread Junio C Hamano
Johannes Schindelin writes: >> > The corresponding times for me were: >> > >> > (master) (with the series) >> >real0m9.760s real 0m5.744s >> >user0m0.531s user 0m0.656s >> >sys 0m5.726s sys 0m3.520s

Re: [PATCH v3 00/34] libify mailinfo and call it directly from am

2015-10-26 Thread Johannes Schindelin
Hi, On Wed, 21 Oct 2015, Johannes Sixt wrote: > Am 21.10.2015 um 17:51 schrieb Ramsay Jones: > > On 20/10/15 22:24, Junio C Hamano wrote: > > > Junio C Hamano writes: > > > some numbers on my desktop (Dell T3500 2.66GHz Xeon X5650 with 12GB, > > > running Ubuntu), > > > > I

Re: [PATCH v3 00/34] libify mailinfo and call it directly from am

2015-10-21 Thread Ramsay Jones
On 20/10/15 22:24, Junio C Hamano wrote: > Junio C Hamano writes: > >> During the discussion on the recent "git am" regression, I noticed >> that the command reimplemented in C spawns one "mailsplit" and then >> spawns "mailinfo" followed by "apply --index" to commit the

Re: [PATCH v3 00/34] libify mailinfo and call it directly from am

2015-10-21 Thread Johannes Sixt
Am 21.10.2015 um 17:51 schrieb Ramsay Jones: On 20/10/15 22:24, Junio C Hamano wrote: Junio C Hamano writes: some numbers on my desktop (Dell T3500 2.66GHz Xeon X5650 with 12GB, running Ubuntu), I suspect that I haven't tested exactly the same version as you, but I had a

Re: [PATCH v3 00/34] libify mailinfo and call it directly from am

2015-10-21 Thread Junio C Hamano
Johannes Sixt writes: > Am 21.10.2015 um 17:51 schrieb Ramsay Jones: >> On 20/10/15 22:24, Junio C Hamano wrote: >>> >>> time git am mbox >/dev/null >>> >>> are >>> >>>(master) (with the series) >>> real0m0.648sreal0m0.537s >>>

Re: [PATCH v3 00/34] libify mailinfo and call it directly from am

2015-10-20 Thread Junio C Hamano
Junio C Hamano writes: > During the discussion on the recent "git am" regression, I noticed > that the command reimplemented in C spawns one "mailsplit" and then > spawns "mailinfo" followed by "apply --index" to commit the changes > described in each message. As there are

Re: [PATCH v3 00/34] libify mailinfo and call it directly from am

2015-10-20 Thread Stefan Beller
On Tue, Oct 20, 2015 at 2:24 PM, Junio C Hamano wrote: > Junio C Hamano writes: > >> During the discussion on the recent "git am" regression, I noticed >> that the command reimplemented in C spawns one "mailsplit" and then >> spawns "mailinfo" followed by

Re: [PATCH v3 00/34] libify mailinfo and call it directly from am

2015-10-20 Thread Junio C Hamano
Stefan Beller writes: > As far as I understand, this only helps for mailing list workflows, which > in my limited view of the world is only found in established infrastructure > projects, who tend to be maintained by people who run some kind of > ab-nomination of unix. >

Re: [PATCH v3 00/34] libify mailinfo and call it directly from am

2015-10-20 Thread Stefan Beller
On Tue, Oct 20, 2015 at 3:06 PM, Junio C Hamano wrote: > Stefan Beller writes: > >> As far as I understand, this only helps for mailing list workflows, which >> in my limited view of the world is only found in established infrastructure >> projects, who

[PATCH v3 00/34] libify mailinfo and call it directly from am

2015-10-19 Thread Junio C Hamano
During the discussion on the recent "git am" regression, I noticed that the command reimplemented in C spawns one "mailsplit" and then spawns "mailinfo" followed by "apply --index" to commit the changes described in each message. As there are platforms where spawning subprocess via run_command()