Hello,
Michael J Gruber wrote:
|Steffen Nurpmeso venit, vidit, dixit 22.09.2016 00:46:
|> Junio C Hamano wrote:
|>|Steffen Nurpmeso writes:
...
|>|I think this issue does not need a separate bullet point. The
|>|existing text says:
|> ..
|>|and what caused your surprise is already cov
Steffen Nurpmeso venit, vidit, dixit 22.09.2016 00:46:
> Junio C Hamano wrote:
> |Steffen Nurpmeso writes:
> ...
> |Sorry, but I did not notice that there was an attached patch when I
> |was reading your response for the first time. Risk of using an
> |attachment to e-mail ;-)
> |
> |I th
Junio C Hamano wrote:
|Steffen Nurpmeso writes:
...
|Sorry, but I did not notice that there was an attached patch when I
|was reading your response for the first time. Risk of using an
|attachment to e-mail ;-)
|
|I think this issue does not need a separate bullet point. The
|existing t
Steffen Nurpmeso writes:
> diff --git a/Documentation/git-ls-tree.txt b/Documentation/git-ls-tree.txt
> index dbc91f9..8ebeced 100644
> --- a/Documentation/git-ls-tree.txt
> +++ b/Documentation/git-ls-tree.txt
> @@ -33,6 +33,10 @@ in the current working directory. Note that:
> However, the c
Hello.
Junio C Hamano wrote:
|Steffen Nurpmeso writes:
|> I think this behaviour contradicts the manual which strongly links
|> ls-tree to ls(1):
|
|Patches to the documentation is very much welcomed.
The below could serve this purpose.
|Somewhere the similarity must end, and actually it
Steffen Nurpmeso writes:
> I think this behaviour contradicts the manual which strongly links
> ls-tree to ls(1):
Patches to the documentation is very much welcomed.
Somewhere the similarity must end, and actually it ends a lot
earlier, as "/bin/ls" takes exact paths while "ls-tree" (or any
oth
6 matches
Mail list logo
