From: Jakub Narebski <jnareb@gmail.com>
To: Michal Nazarewicz <mina86@tlen.pl>
Cc: git@vger.kernel.org
Subject: Re: Something like $Id$, $Revision$ or $Date$?
Date: Mon, 10 Nov 2008 19:03:27 +0100 [thread overview]
Message-ID: <200811101903.27685.jnareb@gmail.com> (raw)
In-Reply-To: <8763mvlbwb.fsf@erwin.mina86.com>
Dnia poniedziałek 10. listopada 2008 18:38, Michal Nazarewicz napisał:
> Jakub Narebski <jnareb@gmail.com> writes:
>
> > The reason why git doesn't support keywords like $Revision$ or $Date$
> > is performance: the $Revision$ and $Date$ are keywords related to
> > _commit_ data, not blob data.
>
> In my case identifying content not commit would be even better.
Well, in that case using `ident` attribute would be enough
(but cryptic).
# set `ident` attribute for all files
$ echo '* ident' > .gitattributes
# check that it is set for file 'foo'
$ git check-attr ident -- foo
foo: ident: set
# edit file to contain '$Id$' keyword
$ cat foo
...
... $Id$ ...
...
# make a commit
$ git commit -a
# $Id$ keyword is replaced on checkout
$ git add foo
$ git checkout foo
# and check that it got replaced
$ cat foo
...
... $Id: 0ca1524d4460ba6bc91bf3adc9dab13212599243 $ ...
...
But you need git to make use of this SHA-1 _blob_ (contents) identifier
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-11-10 18:05 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-10 0:22 Something like $Id$, $Revision$ or $Date$? Michal Nazarewicz
2008-11-10 0:43 ` Sverre Rabbelier
2008-11-10 1:16 ` Michal Nazarewicz
2008-11-10 3:43 ` dhruva
2008-11-10 9:49 ` Michal Nazarewicz
2008-11-10 7:26 ` Johannes Sixt
2008-11-10 12:25 ` Johannes Schindelin
2008-11-10 14:05 ` dhruva
2008-11-10 15:48 ` Michal Nazarewicz
2008-11-10 15:58 ` Francis Galiegue
2008-11-10 15:59 ` Jakub Narebski
2008-11-10 17:38 ` Michal Nazarewicz
2008-11-10 18:03 ` Jakub Narebski [this message]
2008-11-10 20:00 ` Michal Nazarewicz
2008-11-10 20:17 ` Jakub Narebski
2008-11-10 20:24 ` Francis Galiegue
2008-11-10 20:32 ` Jakub Narebski
2008-11-10 20:58 ` Brian Gernhardt
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=200811101903.27685.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
--cc=mina86@tlen.pl \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.