Re: [kernel.org users] [RFD] On deprecating "git-foo" for builtins

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

 




On Sat, 23 Aug 2008, Junio C Hamano wrote:
> 
> There is one alternative, and one augmentation:
> 
>  (A) We do not do anything.
> 
>  (B) In addition to the main transition plan, outside git, prepare an
>      optional "git-old-style" package that installs many "git-foo"
>      wrappers in $PATH (i.e. /usr/bin).  Each of them exec "git foo".
>      People who like the dashed form can keep typing "git-foo", even
>      though that will cost them two exec()s.

I actually suspect that (A) is fine.

I suggested removing the "git-xyzzy" hardlinks entirely, but that was just 
because I didn't think anybody wanted them.

But given that with the 1.6.0 model you can always just do

	PATH="PATH:$(git --exec-path)"

in your .bashrc or similar to get the git-xyzzy form, and given that 
clearly some people like using them, there's really no downside to keeping 
them.

I _would_ suggest against putting them in /usr/bin, even as a 
"compatibility plan". Just expose them to people who want them, who can 
really quite easily do the above PATH setting.

		Linus
--
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