git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Kris Shannon <kris@shannon.id.au>
To: Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: On git 1.6 (novice's opinion)
Date: Wed, 1 Apr 2009 13:32:21 +1100	[thread overview]
Message-ID: <e51f4f550903311932x118e1378yc1b25e5d9c97d50d@mail.gmail.com> (raw)
In-Reply-To: <49CC8C90.12268.242CEFCE@Ulrich.Windl.rkdvmks1.ngate.uni-regensburg.de>

2009/3/27 Ulrich Windl <ulrich.windl@rz.uni-regensburg.de>:
> 2) Keyword substitution. I know it's controverse (dealing with binary files),
> but I'd like to have some automatic version numbering keyword at least:
> Initial idea is that every commit with a change increments the number by one,
> and when merging numbers a and b, the resulting number is max(a, b) + 1.

Check out gitattributes(5) - the ident attribute:

When the attribute ident is set for a path, git replaces $Id$ in the blob
object with $Id:, followed by the 40-character hexadecimal blob object name,
followed by a dollar sign $ upon checkout. Any byte sequence that begins
with $Id: and ends with $ in the worktree file is replaced with $Id$ upon
check-in.

That means the Id is file specific, not commit specific - just like the $Id$
expansion for CVS and SCCS is about the file (as there is no real concept
of a commit in CVS and SCCS)

      parent reply	other threads:[~2009-04-01  2:34 UTC|newest]

Thread overview: 49+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-27  7:21 On git 1.6 (novice's opinion) Ulrich Windl
2009-03-27  8:05 ` H.Merijn Brand
2009-03-27  9:50   ` Ulrich Windl
2009-03-27 10:57     ` Etienne Vallette d'Osia
2009-03-27 11:30       ` Etienne Vallette d'Osia
2009-03-27 12:24     ` Dmitry Potapov
2009-03-27 13:39       ` Ulrich Windl
2009-03-27 13:45         ` Matthieu Moy
2009-03-27 13:47         ` Etienne Vallette d'Osia
2009-04-01  6:50           ` Ulrich Windl
2009-04-01  7:41             ` Matthieu Moy
2009-03-28  1:30         ` Junio C Hamano
2009-03-28  1:30       ` Junio C Hamano
2009-03-28  9:53         ` Dmitry Potapov
2009-03-30  6:18     ` Russ Dill
2009-04-01  7:53       ` Ulrich Windl
2009-04-01  8:37         ` Andreas Ericsson
2009-04-01  9:47           ` Ulrich Windl
2009-04-01 10:17             ` Andreas Ericsson
2009-04-01 20:37             ` Heiko Voigt
2009-03-27 12:24 ` Dmitry Potapov
2009-03-27 13:35   ` Ulrich Windl
2009-03-27 13:44     ` Matthieu Moy
2009-04-01  6:45       ` Ulrich Windl
2009-04-01  7:42         ` Matthieu Moy
2009-03-27 12:49 ` Michael J Gruber
2009-03-27 13:48   ` Ulrich Windl
2009-03-27 14:09     ` Jakub Narebski
2009-04-01  6:59       ` Ulrich Windl
2009-04-01  7:29         ` Andreas Ericsson
2009-04-01  7:54         ` Matthieu Moy
2009-04-01  9:38           ` Ulrich Windl
2009-04-01 10:10             ` Andreas Ericsson
2009-04-02  2:17         ` Jakub Narebski
2009-03-28 10:33     ` demerphq
2009-03-28  1:30 ` Junio C Hamano
2009-04-01  7:35   ` Ulrich Windl
2009-03-29  5:41 ` Bryan Donlan
2009-03-29  9:50   ` Johannes Schindelin
2009-04-01  7:42     ` Ulrich Windl
2009-04-01  7:40   ` Ulrich Windl
2009-03-30  9:06 ` Andreas Ericsson
2009-04-01  8:15   ` Ulrich Windl
2009-04-01  8:41     ` Andreas Ericsson
2009-04-01  9:55       ` Ulrich Windl
2009-04-01 10:21         ` Andreas Ericsson
2009-04-01 11:52           ` Ulrich Windl
2009-04-01 12:40             ` Andreas Ericsson
2009-04-01  2:32 ` Kris Shannon [this message]

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=e51f4f550903311932x118e1378yc1b25e5d9c97d50d@mail.gmail.com \
    --to=kris@shannon.id.au \
    --cc=git@vger.kernel.org \
    --cc=ulrich.windl@rz.uni-regensburg.de \
    /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).