The SYNOPSIS lists the [--no-index] form as the last item, but the
DESCRIPTION lists it as a natural extension of the first form. Fix
this with a reordering. Also since the DESCRIPTION breaks up the
first form in the SYNOPSIS into two different forms (one without the
optional [commit], and the
Ramkumar Ramachandra artag...@gmail.com writes:
The SYNOPSIS lists the [--no-index] form as the last item, but the
DESCRIPTION lists it as a natural extension of the first form.
Perhaps either the description or your reading is wrong.
The --no-index mode was a hack to allow git diff goodies
Junio C Hamano wrote:
The --no-index mode was a hack to allow git diff goodies to be
used outside the context of git, and a proper execution of it
should have been to send patches to GNU or BSD diff maintainers, not
to add the --no-index option that is unrelated to git to our
code.
Yeah, I
Ramkumar Ramachandra wrote:
The form is a special case of
the first form where the number of paths are limited to two. Besides,
isn't that how the DESCRIPTION section explains it now?
Sort of. It's a completely different form, but when --no-index is
Jonathan Nieder wrote:
Maybe it would make sense to move towards eliminating the implicit
--no-index for paths outside the repository trick. I use git diff
--no-index all the time, but I always spell it out to be careful.
Huh? Why do you want to endure the pain of spelling it out, when your
Ramkumar Ramachandra wrote:
Jonathan Nieder wrote:
Maybe it would make sense to move towards eliminating the implicit
--no-index for paths outside the repository trick. I use git diff
--no-index all the time, but I always spell it out to be careful.
Huh? Why do you want to endure the pain
Jonathan Nieder wrote:
Oh please no.
If I understand this correctly, you are horrified by this?
https://github.com/artagnon/dotfiles/blob/master/.gitconfig#L30
By the way, my zsh aliases git to g.
--
To unsubscribe from this list: send the line unsubscribe git in
the body of a message to
Ramkumar Ramachandra wrote:
Jonathan Nieder wrote:
Oh please no.
If I understand this correctly, you are horrified by this?
https://github.com/artagnon/dotfiles/blob/master/.gitconfig#L30
Nope, that looks like a useful way to save typing, and git help
helpfully expands any of your custom
Jonathan Nieder wrote:
Because typing paths does not make my intent perfectly clear.
I'm not able to understand this. Doesn't your prompt tell you which
directory you're in, and if you're in a git repository? When you type
out paths, you know what is inside and what is outside your
repository.
Ramkumar Ramachandra wrote:
Jonathan Nieder wrote:
Because typing paths does not make my intent perfectly clear.
I'm not able to understand this. Doesn't your prompt tell you which
directory you're in, and if you're in a git repository? When you type
out paths, you know what is inside and
Jonathan Nieder wrote:
* hard to document
[...]
I completely disagree, but we don't have to agree: make it a
configuration variable. Even if it's turned to never by default, I
don't mind having one extra line in my .gitconfig. But you went all
Oh please no when I brought it up. I thought
Ramkumar Ramachandra wrote:
I completely disagree, but we don't have to agree: make it a
configuration variable.
I thought we had discussed before how every configuration variable
costs quite a lot in terms of Git's teachability.
What would that configuration variable even mean? Set this to
12 matches
Mail list logo