[prev in list] [next in list] [prev in thread] [next in thread]
List: subversion-issues
Subject: =?UTF-8?B?W0lzc3VlIDIxMDddIE5ldyAtIE5vLW9wIHVwZGF0ZSB0byBrZXl3bw==?=
From: cmpilato () tigris ! org
Date: 2004-10-25 16:16:48
Message-ID: 20041025161648.10000.qmail () tigris ! org
[Download RAW message or body]
http://subversion.tigris.org/issues/show_bug.cgi?id=2107
Issue #:|2107
Summary:|No-op update to keyword-bearing files should trigger
|keyword re-expansion.
Component:|subversion
Version:|trunk
Platform:|All
URL:|
OS/Version:|All
Status:|NEW
Status whiteboard:|
Keywords:|
Resolution:|
Issue type:|DEFECT
Priority:|P3
Subcomponent:|libsvn_wc
Assigned to:|issues@subversion
Reported by:|cmpilato
------- Additional comments from cmpilato@tigris.org Mon Oct 25 09:16:48 -0700 2004 -------
libsvn_wc is forgetting that even no-op changes to a file are still changes.
Most of this time this doesn't matter, but when there are commit info keywords
present, this can cause problems. I have verified that server is sending the
right editor commands (open_file; close_file). I believe the culprit is
install_file(), but don't have the time to dig any further. I do have a nifty
recipe though.
#!/bin/sh
rm -rf repos wc-1 wc-2
svnadmin create repos
svn co -q file://`pwd`/repos wc-1
echo '$Rev$' > wc-1/file
svn add -q wc-1/file
svn pset -q svn:keywords Rev wc-1/file
svn ci -q -m 'r1' wc-1
svn co -q file://`pwd`/repos wc-2
svn pset -q foo bar wc-1/file
svn ci -q -m 'r2' wc-1/
svn pdel -q foo wc-1/file
svn ci -q -m 'r3' wc-1
svn up -q wc-2
echo "The keyword in the following file (wc-2/file) should have revision 3:"
cat wc-2/file
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@subversion.tigris.org
For additional commands, e-mail: issues-help@subversion.tigris.org
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic