Philip Martin <philip.mar...@wandisco.com> writes: > vijayaguru <vi...@collab.net> writes: > >> In 1.5.x & 1.6.x, the keyword is expanded for the first update and >> timestamp is changed for further updates. Here We are just locking the >> file with keywords property set and we are not committing the file.Then >> running "svn update" should expand the keyword & change the timestamp? >> >> But in 1.4.x , the keyword will not expand and timestamp won't >> change for first update. > > It's a change in behaviour but is it a bug? Why should the keyword > remain unexpanded?
>From http://subversion.tigris.org/issues/show_bug.cgi?id=3471 Take a plain versioned file and add a keyword: $ echo '$Id' >> wc/f $ svn ps svn:keywords id wc/f $ svn up wc should update expand the keyword? It doesn't at present, but if I lock the file then the expansion happens. Obviously it's a bug that lock makes a difference. But which is the correct behaviour? To ignore the local property setting or to expand the keyword? What about svn:eol-style? If I do both $ svn ps svn:keywords id wc/f $ svn ps svn:keywords CRLF wc/f then update changes the line-endings when the file is locked (even if the '$Id$' token is not present in the file) but does not change the line-endings if the file is not locked. In this case svn:eol-style only has an effect if svn:keywords is also set. -- Philip
