Re: UNS: Autoconf for CRM114 fun and games

Jimmy Tang wrote:
> Hi,
>
> On Sat, Feb 07, 2009 at 07:49:45AM -0500, Nico Kadel-Garcia wrote:
>   
>> * There ware a bunch of hooks for CVS repository integration, to 
>> generate release numbers, record logs, etc. The problem for me is that 
>> I'm not using CVS, I'm using git. git does not support '$Id$', for 
>> example, and for a bunch of good reasons discussed at considerable 
>> length in the git developer lists.  And of course my git repository does 
>> not have Joost's change history. In theory, I could integrate the change 
>> hsitory in, with a bit of work, but I'm not sure it's really needed. 
>> Does anyone feel attached to the use of $Id$ or CVS? Joost, if you're 
>> out there, if I can get you a git repository, would you consider 
>> migrating to it? Migration is actually pretty easy!
>>     
>
> in relation to the $Id$ variable, you could probably do what the git repo
> of git does with the GIT-VERSION-FILE file and the script that generates a
> version number/name based on a tag name and the number of commits since
> the tag (and or commit id).
>
>
>
> jimmy
>   
Are you referring to the 'GIT-VERSION-GEN' and GIT-VERSION-FILE vagaries 
discussed by Junio C. Hamano, at 
http://marc.info/?l=git&m=113573084515937&w=2? That's.... not quite the 
same thing as $Id$. That's storing  a made up minor release number, 
based on the number of commits, much as Subversion uses a revision 
number that can be parsed in a similar way for an entire repository. I 
hadn't gotten as far as pursuing that: I'm thinking "when Bill wants a 
release, and it goes in the repo, make a tag and GPG sign it for reference".

$Id$ refers to when individual *files* were last modified in a 
repository, and the file name, automatically generated without external 
scripts. It's rather a different function. And Joost's CVS repository 
is, understandably for CVS development, festooned with $Id$.

------------------------------------------------------------------------------
Create and Deploy Rich Internet Apps outside the browser with Adobe(R)AIR(TM)
software. With Adobe AIR, Ajax developers can use existing skills and code to
build responsive, highly engaging applications that combine the power of local
resources and data with the reach of the web. Download the Adobe AIR SDK and
Ajax docs to start building applications today-http://p.sf.net/sfu/adobe-com