On Mon, 26 Nov 2007, Junio C Hamano wrote: > Nicolas Pitre <nico@xxxxxxx> writes: > > > On Mon, 26 Nov 2007, Junio C Hamano wrote: > > > >> Wincent Colaiuta <win@xxxxxxxxxxx> writes: > >> > >> > For the benefit of newcomers, I just wish the plumbing was kept a > >> > little bit out of sight. You know, porcelain in /usr/bin and plumbing > >> > in /usr/libexec or other such place. > >> > > >> > It's fine once you've learnt your workflows and know the 10 or 15 Git > >> > tools that you'll be using day-to-day; but for people who are just > >> > starting off this can be a little bit intimidating: > >> > > >> > $ git-<tab> > >> > Display all 146 possibilities? (y or n) > >> > >> I'd agree to that but I've always considered this an issue for distros. > >> We've supported an ability for them to specify a gitexecdir separate > >> from /usr/bin in our Makefile for almost two years. > > > > Would probably be a good thing to start enforcing that by default. It's > > easier to follow such policies when they're coordinated from the project > > origin. > > Not really. The project origin ships the Makefile to install under > $HOME, but I do not see any distros following that. What about the default RPM spec file? Nicolas - 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
