Re: RFC: a plugin architecture for git extensions?

From: Drew Northup <drew.northup@maine.edu>
Date: Apr 27, 2011, 20:16 UTC
Message-ID: <1303935396.25134.79.camel@drew-northup.unet.maine.edu>
In-Reply-To: <20110427194233.GA16717@gnu.kitenet.net>

On Wed, 2011-04-27 at 15:42 -0400, Joey Hess wrote:

Show 15 quoted lines

> Drew Northup wrote:
> > 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).
> 
> If git-amp is available in $PATH, 'git help amp' runs 'man git-amp'.
> Otherwise, it runs 'man gitamp'.

That's what I thought too, but it didn't work! (<still scratching head here>) I'll have to try a couple of other ways to break it later on.

> Tools like autoconf etc already know how to install man pages into the
> right places. I don't see the need for any additional support for git
> here.

I'm not saying there should be--in fact quite the opposite.

-- 
-Drew Northup
________________________________________________
"As opposed to vegetable or mineral error?"
-John Pescatore, SANS NewsBites Vol. 12 Num. 59