[issue2303] Wrong keyword extending when cloning
Mitar
bugs at mercurial.selenic.com
Sun Jul 25 17:30:41 UTC 2010
New submission from Mitar <mmitar at gmail.com>:
Keyword extending when cloning does not work as expected. When I clone it
does not take into the account my custom configuration of keywords. So on
destination default keywords (which I do not want) are expanded when
cloning, but then hg finds this changes as normal changes in repository.
I am using Mercurial 1.3.1-1~bpo50+2 (Debian backports package). I have
tested also on 1.5.2-1 and 1.6-2 versions (Debian testing and
unstable). I have also tested on Mac OS X with 1.5.4 version.
Example:
hg init repo1
cd repo1
cat << __EOF__ > .hg/hgrc
[extensions]
hgext.graphlog =
color =
keyword =
[keyword]
* =
[keywordmaps]
HgDate = {date|utcdate}
__EOF__
cat << __EOF__ > file
# \$Id: foobar \$
__EOF__
hg add
hg ci -m 'file'
cd ..
hg clone repo1 repo2
cd repo2
hg diff
Output:
hg diff
diff -r d59d36487d1c file
--- a/file Sun Jul 25 15:19:26 2010 +0200
+++ b/file Sun Jul 25 15:19:34 2010 +0200
@@ -1,1 +1,1 @@
-# $Id: foobar $
+# $Id: file,v d59d36487d1c 2010/07/25 13:19:26 root $
Globally and on the user level keyword extension is not enabled in
configuration. Only in source repository extension is enabled. So why
does it extend "Id" keyword as it is shown by diff command.
----------
messages: 13215
nosy: mitar
priority: bug
status: unread
title: Wrong keyword extending when cloning
____________________________________________________
Mercurial issue tracker <bugs at mercurial.selenic.com>
<http://mercurial.selenic.com/bts/issue2303>
____________________________________________________
More information about the Mercurial-devel
mailing list