git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: Andreas Hildebrandt <anhi@bioinf.uni-sb.de>, git@vger.kernel.org
Subject: Re: CVS-$Id:$ replacement in git?
Date: Fri, 31 Aug 2007 18:12:33 +0100 (BST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0708311812000.28586@racer.site> (raw)
In-Reply-To: <7v8x7r1wyy.fsf@gitster.siamese.dyndns.org>

Hi,

On Fri, 31 Aug 2007, Junio C Hamano wrote:

> Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:
> 
> > On Fri, 31 Aug 2007, Andreas Hildebrandt wrote:
> >
> >> But unfortunately, we internally rely heavily on the $Id:$ - expansion 
> >> of CVS, that is the ability to have a line like
> >> 
> >> $Id:$
> >> 
> >> in the source file expanded to something like
> >> 
> >> $Id: HINFile.C,v 1.64 2005/02/09 13:02:41 oliver Exp $
> >> 
> >> The information we want to store in the file would be something like the 
> >> SHA1 of the last commit that touched that file, the date when it 
> >> happened and the person who commited it.
> >
> > Please see Documentation/gitattributes.txt, look for 'ident'.
> 
> Please do _not_ see that.  ident is about blob object name and
> does not have anything to do with the commit, pathname,
> committer, nor date, and this is deliberately so.

But this is what I was suggesting...  To change the ways for the better.  
I admit that I was really sneaky about it.

Ciao,
Dscho

  parent reply	other threads:[~2007-08-31 17:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-31 15:03 CVS-$Id:$ replacement in git? Andreas Hildebrandt
2007-08-31 16:33 ` Johannes Schindelin
2007-08-31 16:37   ` Junio C Hamano
2007-08-31 16:58     ` Rogan Dawes
2007-08-31 17:12     ` Johannes Schindelin [this message]
2007-08-31 18:45       ` Junio C Hamano

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=Pine.LNX.4.64.0708311812000.28586@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=anhi@bioinf.uni-sb.de \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).