Re: [PATCH v2 08/14] sequencer: lib'ify read_and_refresh_cache()

2016-08-30 Thread Junio C Hamano
Johannes Schindelin writes: >> With the current set of callers, a caller that notices an error from >> this function will immediately exit without doing any further >> damage. >> >> So in that sense, this is a "safe" conversion. >> >> But is it a sensible conversion? When the caller wants to d

Re: [PATCH v2 08/14] sequencer: lib'ify read_and_refresh_cache()

2016-08-30 Thread Johannes Schindelin
Hi Junio, On Mon, 29 Aug 2016, Junio C Hamano wrote: > Johannes Schindelin writes: > > > Instead of dying there, let the caller high up in the callchain > > notice the error and handle it (by dying, still). > > > > There are two call sites of read_and_refresh_cache(), one of which is > > pick_c

Re: [PATCH v2 08/14] sequencer: lib'ify read_and_refresh_cache()

2016-08-29 Thread Junio C Hamano
Johannes Schindelin writes: > Instead of dying there, let the caller high up in the callchain > notice the error and handle it (by dying, still). > > There are two call sites of read_and_refresh_cache(), one of which is > pick_commits(), whose callers were already prepared to do the right > thing

[PATCH v2 08/14] sequencer: lib'ify read_and_refresh_cache()

2016-08-26 Thread Johannes Schindelin
Instead of dying there, let the caller high up in the callchain notice the error and handle it (by dying, still). There are two call sites of read_and_refresh_cache(), one of which is pick_commits(), whose callers were already prepared to do the right thing given an "error" return from it by an ea