git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Todd A. Jacobs" <nospam@codegnome.org>
To: git@vger.kernel.org
Subject: Integrating with hooks
Date: Tue, 13 Nov 2007 09:37:21 -0800	[thread overview]
Message-ID: <20071113173721.GI25282@penguin.codegnome.org> (raw)

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:

    # Show some kind of useful revision string, like the RCS $Id$ string. I
    # think commit hash, filename, hostname containing the repository, and
    # timestamp should be plenty of information to track down a given file.
    git-id () {
	for file in "$@"; do
	    _date=$(date +'%F %T %Z')
	    git log -1 \
		--pretty=format:"[%h] \"$file\" $(hostname -f) ($_date)" \
		"$file"
	done
    }
    # Replace the $Id$ keyword string in the file itself.
    git-export () {
	for file in "$@"; do
	    echo Modifying $file...
	    _id=$(git-id "$file")
	    sed -ri 's/\$(Id|Revision).*\$/$Id: '"$_id"' $/' "$file"
	done
    }
    # Clean the $Id$ keyword string to prevent cluttering the repository
    # with keyword-revision diffs when we check the file back in.
    git-unexport () {
	for file in "$@"; do
	    echo Resetting $file...
	    sed -ri 's/\$Id.*\$/$Id$/' "$file"
	done
    }

How do I hook this in the way I want so that it's handled automatically?

-- 
"Oh, look: rocks!"
	-- Doctor Who, "Destiny of the Daleks"

             reply	other threads:[~2007-11-13 20:42 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-13 17:37 Todd A. Jacobs [this message]
2007-11-13 23:07 ` Integrating with hooks Jakub Narebski
2007-11-15  1:18   ` Todd A. Jacobs
2007-11-15  1:43     ` Jakub Narebski
2007-11-15  1:43     ` Johannes Schindelin
2007-11-15  7:57     ` Johannes Sixt

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20071113173721.GI25282@penguin.codegnome.org \
    --to=nospam@codegnome.org \
    --cc=git@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).