Am 24.10.2017 um 02:52 schrieb Junio C Hamano:
> René Scharfe writes:
>
>> Am 21.10.2017 um 14:18 schrieb Junio C Hamano:
>>> René Scharfe writes:
>>>
FWIW, I use "-?" for that everywhere. I have yet to find a command or
environment where it does something
René Scharfe writes:
> Am 21.10.2017 um 14:18 schrieb Junio C Hamano:
>> René Scharfe writes:
>>
>>> FWIW, I use "-?" for that everywhere. I have yet to find a command or
>>> environment where it does something dangerous.
>>
>> Yeah, it would have made the world a
Am 21.10.2017 um 14:18 schrieb Junio C Hamano:
> René Scharfe writes:
>
>> FWIW, I use "-?" for that everywhere. I have yet to find a command or
>> environment where it does something dangerous.
>
> Yeah, it would have made the world a better place if we made that
> choice back
René Scharfe writes:
> FWIW, I use "-?" for that everywhere. I have yet to find a command or
> environment where it does something dangerous.
Yeah, it would have made the world a better place if we made that
choice back in 2008. If we start a transition to make it so right
now,
Am 20.10.2017 um 07:35 schrieb Junio C Hamano:
> Jeff King writes:
>
>> It seems weird and inconsistent to me that the meaning of "-h"
>> depends on the position and presence of other unrelated options.
The position is relevant with parse-options for *each* flag for a
different
On Fri, Oct 20, 2017 at 02:35:36PM +0900, Junio C Hamano wrote:
> I may be biased as every time I think about this one, the first one
> that comes to my mind is how "grep -h" (not "git grep", but GNU
> grep) behaves. Yes, "-h" means something else, but by itself, the
> command does not make
Jeff King writes:
> It seems weird and inconsistent to me that the meaning of "-h"
> depends on the position and presence of other unrelated options. Maybe
> it's just me. I know _why_ it's that way, but this seems like one of
> those weird corners of the interface that end up
On Fri, Oct 20, 2017 at 10:04:23AM +0900, Junio C Hamano wrote:
> > Yuck. This "we only treat -h as special in certain cases" rule is
> > sufficiently magical that I don't think we want to advertise and lock
> > ourselves into it.
>
> Hmph. I think it is way too late to be worried about "locked
Jeff King writes:
> On Thu, Oct 19, 2017 at 08:26:47PM +0200, René Scharfe wrote:
>
>> diff --git a/Documentation/git-ls-remote.txt
>> b/Documentation/git-ls-remote.txt
>> index 5f2628c8f8..82622e7fbc 100644
>> --- a/Documentation/git-ls-remote.txt
>> +++
On Thu, Oct 19, 2017 at 08:26:47PM +0200, René Scharfe wrote:
> diff --git a/Documentation/git-ls-remote.txt b/Documentation/git-ls-remote.txt
> index 5f2628c8f8..82622e7fbc 100644
> --- a/Documentation/git-ls-remote.txt
> +++ b/Documentation/git-ls-remote.txt
> @@ -29,6 +29,9 @@ OPTIONS
>
Am 18.10.2017 um 01:22 schrieb Junio C Hamano:
> René Scharfe writes:
>
>> Stop advertising -h as the short equivalent of --heads, because it's
>> used for showing a short help text for almost all other git commands.
>> Since the ba5f28bf79 (ls-remote: use parse-options api) it has
René Scharfe writes:
> Stop advertising -h as the short equivalent of --heads, because it's
> used for showing a short help text for almost all other git commands.
> Since the ba5f28bf79 (ls-remote: use parse-options api) it has only
> been working when used together with other
René Scharfe wrote:
> Stop advertising -h as the short equivalent of --heads, because it's
> used for showing a short help text for almost all other git commands.
> Since the ba5f28bf79 (ls-remote: use parse-options api) it has only
> been working when used together with other parameters anyway.
On 17 October 2017 at 17:39, René Scharfe wrote:
> Stop advertising -h as the short equivalent of --heads, because it's
> used for showing a short help text for almost all other git commands.
> Since the ba5f28bf79 (ls-remote: use parse-options api) it has only
> been working when
Stop advertising -h as the short equivalent of --heads, because it's
used for showing a short help text for almost all other git commands.
Since the ba5f28bf79 (ls-remote: use parse-options api) it has only
been working when used together with other parameters anyway.
Signed-off-by: Rene Scharfe
15 matches
Mail list logo