From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Linus Torvalds <torvalds@osdl.org>,
Liu Yubao <yubao.liu@gmail.com>,
Dongsheng Song <dongsheng.song@gmail.com>,
git@vger.kernel.org
Subject: Re: Does GIT has vc keywords like CVS/Subversion?
Date: Tue, 10 Oct 2006 09:37:57 +0200 [thread overview]
Message-ID: <452B4DD5.6060508@lsrfire.ath.cx> (raw)
In-Reply-To: <46a038f90610091408y29f60a12gea7040b5412331c6@mail.gmail.com>
Martin Langhoff schrieb:
> For the outside of the SCM case, keyword subst is useful indeed if
> someone has a $version_unknown tarball, unpacks it and hacks away. It
> is a pretty broken scenario, and less likely to happen nowadays with
> easy access to SCM tools.
If you still have the tar file, and if it has been created using
git-archive or git-tar-tree it may contain the commit ID in an archive
comment. You can use git-get-tar-commit-id to extract it in that case.
This won't work with official git project tarballs btw., as commit ID
embedding has been turned off. The reason is that older tar versions
extracted the comment as a regular file, which confused users.
René
next prev parent reply other threads:[~2006-10-10 7:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-09 1:25 Does GIT has vc keywords like CVS/Subversion? Dongsheng Song
2006-10-09 2:44 ` Liu Yubao
2006-10-09 2:59 ` Petr Baudis
2006-10-09 16:13 ` Linus Torvalds
2006-10-09 21:08 ` Martin Langhoff
2006-10-09 22:48 ` Johannes Schindelin
2006-10-09 22:57 ` Martin Langhoff
2006-10-09 22:55 ` Junio C Hamano
2006-10-10 7:37 ` Rene Scharfe [this message]
2006-10-10 16:49 ` Shawn Pearce
2006-10-10 17:14 ` Linus Torvalds
2006-10-10 17:41 ` 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=452B4DD5.6060508@lsrfire.ath.cx \
--to=rene.scharfe@lsrfire.ath.cx \
--cc=dongsheng.song@gmail.com \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@gmail.com \
--cc=torvalds@osdl.org \
--cc=yubao.liu@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;
as well as URLs for NNTP newsgroup(s).