Re: [mh] svn-update

[Matthew W. <mat...@us...>]

I've fixed this problem in rev 907.  The fix was to manually parse the
.svn/entries file within the base of the working copy.  If the file is
detected, then the revision of the working copy gets added to the end of the
standard mh $Version.

Now the tricky thing is that the format of .svn/entries is not guaranteed to
remain constant and in fact recently changed in subversion 1.4.  The new
code should take care of both formats, but we'll have to update the code the
next time that the working copy format is updated.

A second "gotcha" is that a subversion commit does not automatically do a
subversion update and only a subversion update from the working copy trunk
will update .svn/entries.  So, if you are a developer, make sure that you do
an svn update after your commits or you won't see the new $Version.

These changes mean that those running from 2.103, when released, will see a
$Version of "mh 2.103" while someone running off revision 2000 will see a
$Version like this "mh 2.105 R2000".

Matt
__________________________________________________
Do You Yahoo!?
Tired of spam?  Yahoo! Mail has the best spam protection around 
http://mail.yahoo.com