On Tue, Apr 17, 2018 at 8:17 PM, Junio C Hamano wrote:
> Eric Sunshine writes:
>> Makes sense. A possible rewrite (of the entire commit message):
>>
>> worktree: remove: recognize -f as short for --force
>>
>> Many commands support a --force
Eric Sunshine writes:
> On Tue, Apr 17, 2018 at 2:19 PM, Stefan Beller wrote:
>> The force flag is very common in many commands and is commonly
>> abbreviated with '-f', so add that to worktree removal, too by using
>> OPT__FORCE instead of a self
On Tue, Apr 17, 2018 at 2:19 PM, Stefan Beller wrote:
> The force flag is very common in many commands and is commonly
> abbreviated with '-f', so add that to worktree removal, too by using
> OPT__FORCE instead of a self cooked OPT_BOOL for force.
The missing bit of this
The force flag is very common in many commands and is commonly
abbreviated with '-f', so add that to worktree removal, too by using
OPT__FORCE instead of a self cooked OPT_BOOL for force.
While at it, add the PARSE_OPT_NOCOMPLETE flag to the force command line
option as forcing a removal may lose
On Mon, Apr 16, 2018 at 6:16 PM, Stefan Beller wrote:
> The force flag is very common in many commands and is commonly
> abbreviated with '-f', so add that to worktree removal, too
>
> Signed-off-by: Stefan Beller
> ---
> diff --git a/builtin/worktree.c
The force flag is very common in many commands and is commonly
abbreviated with '-f', so add that to worktree removal, too
Signed-off-by: Stefan Beller
---
As a side note:
$ git worktree add ../test HEAD^
$ cd ../test
$ make
$ git worktree remove test
fatal: working
6 matches
Mail list logo