git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Use the template mechanism to set up refs/ hierarchy as well.

From
Junio C Hamano <junkio@cox.net>
Date
Aug 4, 2005, 21:35 UTC
Message-ID
<7vmznxwfka.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<Pine.LNX.4.63.0508042311370.24861@wgmdd8.biozentrum.uni-wuerzburg.de>
Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
Show 6 quoted lines
> Sorry, I am so used to not installing in my home because of small quotas 
> :-(
>
> Anyway, my usual setup is that I check git out from my private branch, add 
> that directory to my path, and every once in a while do a "git pull origin 
> && make test". Right now, it works.

Oh, I see. Then the "templates/Makefile building into templates/blt and then installing if you say make install" approach I described earlier would hopefully work perfectly well for you. Just like you tack the $src to your $PATH, you can define GIT_TEMPLATE_DIRECTORY to $src/templates/blt. Problem solved.

Previous: Johannes SchindelinNext: Johannes Schindelin
Message 7 of 10 in “Use the template mechanism to set up refs/ hierarchy as well.”
  1. Use the template mechanism to set up refs/ hierarchy as well.Junio C Hamano, Aug 3, 2005
  2. Johannes SchindelinAug 4, 2005
  3. Junio C HamanoAug 4, 2005
  4. Johannes SchindelinAug 4, 2005
  5. Junio C HamanoAug 4, 2005
  6. Johannes SchindelinAug 4, 2005
  7. Junio C HamanoAug 4, 2005
  8. Johannes SchindelinAug 5, 2005
  9. barkalow@iabervon.orgAug 4, 2005
  10. Junio C HamanoAug 5, 2005

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.