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

Re: Integrating with hooks

From
Jakub Narebski <jnareb@gmail.com>
Date
Nov 13, 2007, 23:07 UTC
Message-ID
<fhdane$kfs$1@ger.gmane.org>
In-Reply-To
<20071113173721.GI25282@penguin.codegnome.org>
[Cc: Todd A. Jacobs <nospam@codegnome.org>, git@vger.kernel.org]
Todd A. Jacobs wrote:
Show 8 quoted lines
> I've created some bash functions which handle tagging some files with
> revision information, but even after reading the git manual I'm not
> really sure how to integrate them so that they remove revision expansion
> before each check-in (to avoid cluttering the repository with keyword
> substitutions), and add them back (with the current commit info) after
> each commit.
> 
> These are the functions:
[...]
> How do I hook this in the way I want so that it's handled automatically?
Take a look at gitattributes(5), namely 'filter' attribute.

Although instead of implementing it "by hand", perhaps it would be enough to use 'ident' and/or 'export-subs' attribute.

P.S. Because of the way git updates files, and git thinks about files it is I think universally regarded to be bad idea to put in a file any Id that depend on commit data.

-- 
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
Previous: Todd A. JacobsNext: Todd A. Jacobs
Message 2 of 6 in “Integrating with hooks”
  1. Todd A. JacobsNov 13, 2007
  2. Jakub NarebskiNov 13, 2007
  3. Todd A. JacobsNov 15, 2007
  4. Jakub NarebskiNov 15, 2007
  5. Johannes SchindelinNov 15, 2007
  6. Johannes SixtNov 15, 2007

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.