Git development
 help / color / mirror / Atom feed
From: Michal Nazarewicz <mina86@tlen.pl>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Something like $Id$, $Revision$ or $Date$?
Date: Mon, 10 Nov 2008 21:00:56 +0100	[thread overview]
Message-ID: <871vxjl5af.fsf@erwin.mina86.com> (raw)
In-Reply-To: <200811101903.27685.jnareb@gmail.com> (Jakub Narebski's message of "Mon, 10 Nov 2008 19:03:27 +0100")

[-- Attachment #1: Type: text/plain, Size: 1278 bytes --]

Jakub Narebski <jnareb@gmail.com> writes:

> 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).

Yes, but it forces me to do some voodoo magic (ie. checkout) to get the
Id in the file, ;) like so:

#v+
$ echo '$Id$' >bar && git add bar && git commit -m 'Added bar' && cat bar
Created commit d49d436: Added bar
 1 files changed, 1 insertions(+), 0 deletions(-)
 create mode 100644 bar
$Id$
$ rm bar && git checkout bar && cat bar
$Id: 055c8729cdcc372500a08db659c045e16c4409fb $
#v-

But never mind, since it seems hard to accomplish in git, I'll have to
learn to live without it. ;)

-- 
Best regards,                                         _     _
 .o. | Liege of Serenly Enlightened Majesty of      o' \,=./ `o
 ..o | Computer Science,  Michal "mina86" Nazarewicz   (o o)
 ooo +--<mina86*tlen.pl>--<jid:mina86*jabber.org>--ooO--(_)--Ooo--

[-- Attachment #2: Type: application/pgp-signature, Size: 196 bytes --]

  reply	other threads:[~2008-11-10 20:02 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
2008-11-10 20:00       ` Michal Nazarewicz [this message]
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=871vxjl5af.fsf@erwin.mina86.com \
    --to=mina86@tlen.pl \
    --cc=git@vger.kernel.org \
    --cc=jnareb@gmail.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