On Wed, 2011-04-27 at 11:28 -0700, Junio C Hamano wrote: > Junio C Hamano <gitster@xxxxxxxxx> writes: > > > Andreas Ericsson <ae@xxxxxx> writes: > > > >> You're utterly horribly wrong. ... > >> ... > >> So the complete description would be > >> > >> git clone git://somerepo/gitworks > >> cd gitworks > >> make install > >> > >> and the rest is in developer hands. > > > > Yeah, I like this as the conclusion of this thread ;-). > > Having said that, to make this work well not just for the command but for > documentation and help, there needs a way for the build procedure of such > user-script project to query the manpage and the documentation paths, just > like we let them query the executable path via "git --exec-path". I was just thinking of that, and for hoots and hollers I copied /usr/share/man/man1/git-am.1.gz to /usr/share/man/man1/git-amp.1.gz and tried "git help amp" on it. [dnorthup@drew-northup ~]$ git help amp No manual entry for gitamp So, that doesn't work. I haven't checked yet how Git "knows" what valid pages are available for "git help" but just putting another file in the same directory as the others didn't do the job (at least not on my workstation). However, as noted earlier, copying /usr/bin/git-am to /usr/bin/git-amp did work. Executing "git amp -h" resulted in the built-in help text for 'git am' being printed to the screen, exactly as expected. -- -Drew Northup ________________________________________________ "As opposed to vegetable or mineral error?" -John Pescatore, SANS NewsBites Vol. 12 Num. 59 -- 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