> -----Original Message-----
> From: Junio C Hamano [mailto:gits...@pobox.com] 
> Sent: Friday, September 14, 2012 4:24 PM
> To: Michael J Gruber
> Cc: Johannes Sixt; Mestnik, Michael J - Eagan, MN - 
> Contractor; git@vger.kernel.org
> Subject: Re: Using Format/export-subst Howto.
> Michael J Gruber <g...@drmicha.warpmail.net> writes:
> > you need to "rm file && git checkout file"). If the user 
> has to update
> > $Id$ to match the current sha1
> > (by remembering to do a more forceful checkout than 
> checkout -f) then
> > one half of that feature is useless. 
> As if there is any value in "$Id$" _feature_.  It's a checkbox item,
> nothing more ;-).

I agree here, $Id$ is much more useful in rcs/cvs.  That's why I chose to dive 
into export-subst, because I wanted my output to not only contain the uniq Id 
of the script but also the time and user of the last edit.

I'm going to read up on export today.  Just for context I'm using git to manage 
daily cron scripts, run on about 1,000 hosts, located on NFS.  I've moved the 
editing of the scripts into user's home directories as I'm a fan of not using 
editors on live data.  The key point is that when sudoing to the shared user 
who manages the files the commands run should be minimal and "pushd; ln -s ... 
.git; git pull; rm .git; popd;" works well.  If I can replace this with 
something that would populate these fields that would be awesome.


Mike Mestnik, Michael J
The ESM Tools
Enterprise Systems Monitoring
United States Postal Service
 O: (651) 406-2048
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to