Or just trigger a build via a built robot or record a commit information
into an issue tracker...

Pascal.

-- 

--|------------------------------------------------------
--| Pascal Obry                           Team-Ada Member
--| 45, rue Gabriel Peri - 78114 Magny Les Hameaux FRANCE
--|------------------------------------------------------
--|              http://www.obry.net
--| "The best way to travel is by means of imagination"
--|
--| gpg --keyserver wwwkeys.pgp.net --recv-key C1082595

-

[ message continues ]

I don't remember if it would be in coming 1.5.4 release, but there
is "git pull --rebase", which means fetch + rebase instead of default
fetch + merge.

HTH
-- 
Jakub Narebski
Poland
ShadeHawk on #git
-

[ message continues ]

That's not a case of "modifying a work tree *after* a commit".

There are many valid uses for post-commit hook and this is one of them. But
like the others it does not modify versioned files. That was the issue
discussed (and pre-commit indeed turned out a better match).

-- 
						 Jan 'Bulb' Hudec <bulb@ucw.cz>
-

[ message continues ]