Stefan Beller writes:
> Upon closer inspection, I have the impression that f389c808b6
> (Rework make_usage to print the usage message immediately,
> 2007-10-14) introduced the extra new line without giving a rationale.
I do not think that is the case. The code before that patch
collected all th
On Fri, Aug 25, 2017 at 1:27 PM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> Currently the worktree command gives its usage, when no subcommand is
>> given. However there are no general options, all options are related to
>> the subcommands itself, such that:
>>
>> #$ git worktree
>>
Stefan Beller writes:
> Currently the worktree command gives its usage, when no subcommand is
> given. However there are no general options, all options are related to
> the subcommands itself, such that:
>
> #$ git worktree
> #usage: git worktree add [] []
> # or: git worktree
Currently the worktree command gives its usage, when no subcommand is
given. However there are no general options, all options are related to
the subcommands itself, such that:
#$ git worktree
#usage: git worktree add [] []
# or: git worktree list []
# or: git worktree loc
Stefan Beller writes:
> Currently the worktree command gives its usage, when no subcommand is
> given. However there are no general options, all options are related to
> the subcommands itself, such that:
>
> $ git worktree
> usage: git worktree add [] []
>or: git worktree list [
Junio C Hamano writes:
> Stefan Beller writes:
>
>> Currently the worktree command gives its usage, when no subcommand is
>> given. However there are no general options, all options are related to
>> the subcommands itself, such that:
>>
>> $ git worktree
>> usage: git worktree add [] [
On Fri, Aug 25, 2017 at 10:18 AM, Junio C Hamano wrote:
> Stefan Beller writes:
>
>> Currently the worktree command gives its usage, when no subcommand is
>> given. However there are no general options, all options are related to
>> the subcommands itself, such that:
>>
>> $ git worktree
>>
Stefan Beller writes:
> Currently the worktree command gives its usage, when no subcommand is
> given. However there are no general options, all options are related to
> the subcommands itself, such that:
>
> $ git worktree
> usage: git worktree add [] []
>or: git worktree list [
Currently the worktree command gives its usage, when no subcommand is
given. However there are no general options, all options are related to
the subcommands itself, such that:
$ git worktree
usage: git worktree add [] []
or: git worktree list []
or: git worktree lock []
9 matches
Mail list logo