Re: [PATCH v2 1/7] log-tree: respect diffopt's configured output file stream

Hi, On Tue, 21 Jun 2016, Johannes Schindelin wrote: > On Tue, 21 Jun 2016, Johannes Schindelin wrote: > > > Expect v3 in a moment. > > I am sorry. The regression test suite just sounded red alert. So: do not > expect v3 in a moment, but later today. So making maybe_flush_or_die() uncovered a p

Re: [PATCH v2 1/7] log-tree: respect diffopt's configured output file stream

Hi, On Tue, 21 Jun 2016, Johannes Schindelin wrote: > Expect v3 in a moment. I am sorry. The regression test suite just sounded red alert. So: do not expect v3 in a moment, but later today. Ciao, Dscho -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to

Re: [PATCH v2 1/7] log-tree: respect diffopt's configured output file stream

Hi Junio, On Mon, 20 Jun 2016, Junio C Hamano wrote: > Johannes Schindelin writes: > > > The diff options already know how to print the output anywhere else > > than stdout. The same is needed for log output in general, e.g. when > > writing patches to files in `git format-patch`. Let's allow

Re: [PATCH v2 1/7] log-tree: respect diffopt's configured output file stream

Johannes Schindelin writes: > The diff options already know how to print the output anywhere else > than stdout. The same is needed for log output in general, e.g. > when writing patches to files in `git format-patch`. Let's allow > users to use log_tree_commit() *without* changing global state v

[PATCH v2 1/7] log-tree: respect diffopt's configured output file stream

The diff options already know how to print the output anywhere else than stdout. The same is needed for log output in general, e.g. when writing patches to files in `git format-patch`. Let's allow users to use log_tree_commit() *without* changing global state via freopen(). Signed-off-by: Johannes