On Tue, 26 Aug 2008, Junio C Hamano wrote:
> Read the subject line again, and notice that we are not talking about
Don't deprecate git-foo and leave them in $gitexecdir as things are now.
That's the best compromise IMHO.
Those who want git-foo can have it via several and easy means. Those
who want 'git foo' have it by default which IMHO is pretty sane (the
other way around is less easy so 'git foo' being the default is the most
sensible alternative).
Platforms where filesystem links are not available simply don't have to
support the git-foo form, period. I doubt users of such platforms will
care much.
All the rest is only bikeshedding.
Nicolas
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
| Christoph Lameter | Re: [RFC 00/15] x86_64: Optimize percpu accesses |
| Linus Torvalds | Re: [Patch v2] Make PCI extended config space (MMCONFIG) a driver opt-in |
| Greg Kroah-Hartman | [PATCH 005/196] Chinese: add translation of SubmittingDrivers |
| Bart Van Assche | Integration of SCST in the mainstream Linux kernel |
git: | |
| David Miller | [GIT]: Networking |
| David Miller | Re: [PATCH] pkt_sched: Destroy gen estimators under rtnl_lock(). |
| Christoph Hellwig | Re: [PATCH 06/32] IGET: Mark iget() and read_inode() as being obsolete [try #2] |
| Gerrit Renker | [PATCH 26/37] dccp: Integration of dynamic feature activation - part 1 (socket set... |
