From: Petr Baudis <pasky@suse.cz>
To: Liu Yubao <yubao.liu@gmail.com>
Cc: Dongsheng Song <dongsheng.song@gmail.com>, git@vger.kernel.org
Subject: Re: Does GIT has vc keywords like CVS/Subversion?
Date: Mon, 9 Oct 2006 04:59:05 +0200 [thread overview]
Message-ID: <20061009025905.GM20017@pasky.or.cz> (raw)
In-Reply-To: <4529B77A.707@gmail.com>
Dear diary, on Mon, Oct 09, 2006 at 04:44:10AM CEST, I got a letter
where Liu Yubao <yubao.liu@gmail.com> said that...
> Dongsheng Song wrote:
> >I want to know whether there is a plan to add this feature, or GIT
> >doesn't require it at all.
> >
> >Keywords like LastChangedDate, LastChangedRevision, LastChangedBy, Id
> >are useful for version control.
> >
> I almost mistake I sent my last question twice:-), maybe we need more FAQs
> like this:
> Q: Does GIT [some feature] like [some vcs] ?
> A: No. Because ...
I have added direct link to FAQ in the Git wiki to the Git homepage
header - http://git.or.cz/gitwiki/GitFaq. It's a wiki, so feel free to
add more q/a there.
> IMHO, I don't think keyword substitution is a good idea, as it will confuse
> the external diff/merge tools.
There can be valid usage scenarios for keyword substitution but I tend
to agree that it usually is not necessary to have it (and projects tend
to use it just "because we can", which is of course their right). Also,
implementing it in Git poses some challenges and has some ugly
implications (like actually having to start to worry about binary
files).
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
#!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj
$/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1
lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/)
next prev parent reply other threads:[~2006-10-09 2:59 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 [this message]
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
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=20061009025905.GM20017@pasky.or.cz \
--to=pasky@suse.cz \
--cc=dongsheng.song@gmail.com \
--cc=git@vger.kernel.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).