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
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.
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
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
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
5 matches
Mail list logo