Re: [PATCH v4 04/44] builtin-am: implement patch queue mechanism

2015-07-07 Thread Paul Tan
On Mon, Jun 29, 2015 at 1:08 PM, Stefan Beller wrote: > (optional nit, bikeshedding) > In conjunction with the previous patch I just wonder when we put a > TODO and when we want to put a NEEDSWORK, or if we're being > inconsistent here as both issues will be resolved in a later patch > in the seri

Re: [PATCH v4 04/44] builtin-am: implement patch queue mechanism

2015-06-28 Thread Stefan Beller
On Sun, Jun 28, 2015 at 7:05 AM, Paul Tan wrote: > git-am applies a series of patches. If the process terminates > abnormally, we want to be able to resume applying the series of patches. > This requires the session state to be saved in a persistent location. > > Implement the mechanism of a "patc

[PATCH v4 04/44] builtin-am: implement patch queue mechanism

2015-06-28 Thread Paul Tan
git-am applies a series of patches. If the process terminates abnormally, we want to be able to resume applying the series of patches. This requires the session state to be saved in a persistent location. Implement the mechanism of a "patch queue", represented by 2 integers -- the index of the cur