Re: [PATCH 0/2] checkout: added two options to control progress output

2015-10-30 Thread Junio C Hamano
Jeff King writes: >> --progress-lf: print progress information using LFs instead of CRs > > I notice this is part of your patch 1, but it really seems orthogonal to > checkout's --progress option. It should probably be a separate patch, > and it probably needs some justification

Re: [PATCH 0/2] checkout: added two options to control progress output

2015-10-29 Thread Jeff King
On Sat, Oct 24, 2015 at 08:59:28AM -0600, Edmundo Carmona wrote: > From: Edmundo Carmona Antoranz > > checkout will refuse to print progress information if it's not connected > to a TTY. These patches will add two options: Not just checkout, but all of git's progress code.

Re: [PATCH 0/2] checkout: added two options to control progress output

2015-10-29 Thread Edmundo Carmona Antoranz
On Thu, Oct 29, 2015 at 4:05 PM, Jeff King wrote: > On Sat, Oct 24, 2015 at 08:59:28AM -0600, Edmundo Carmona wrote: > >> From: Edmundo Carmona Antoranz >> >> checkout will refuse to print progress information if it's not connected >> to a TTY. These patches

Re: [PATCH 0/2] checkout: added two options to control progress output

2015-10-29 Thread Jeff King
On Thu, Oct 29, 2015 at 06:09:06PM -0600, Edmundo Carmona Antoranz wrote: > A comment there: I think more builtins support --progress than the ones that > support --no-progress, right? Hopefully they are supported equally everywhere. Anybody using parseopt should have something like (this is

[PATCH 0/2] checkout: added two options to control progress output

2015-10-24 Thread Edmundo Carmona
From: Edmundo Carmona Antoranz checkout will refuse to print progress information if it's not connected to a TTY. These patches will add two options: --progress-no-tty: enable printing progress info even if not using a TTY --progress-lf: print progress information using LFs