Re: Start deprecating "git-command" in favor of "git command"

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Linus Torvalds <torvalds@xxxxxxxxxxxxxxxxxxxx> writes:

> Well, we have a more serious issue, that is related, but has nothing to do 
> with aliases.
>
> If you set an environment variable "diff.color=always", any script will 
> get that behaviour, and not work the way it might expect.
>
> My point being that this has nothing to do with "git-diff" vs "git diff", 
> and everything to do with default configurations. If you don't want people 
> to be able to change fixed behaviour, you'd need to have a way to disable 
> it.

That's exactly why we have told people to use plumbing in their
scripts, and git-diff-tree does not look at diff.color.

> Quite frankly, I think it's _easier_ to disable with "git xyzzy" than with 
> "git-xyzzy", but hey, not a big deal. With "git xyzzy", we could add a 
> generic flag like
>
> 	git - xyzzy
>
> to make the rule be that no configurations (_including_ aliases) are 
> allowed to override default behaviour, which is much harder with the 
> "git-xyzzy" format (since then it's invariably a per-command thing).

But that would break existing scripts wouldn't it?

-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux