[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: [PATCH] Take 2: Modified export behavior

From: John Szakmeister <john_at_szakmeister.net>
Date: 2003-11-18 13:09:11 CET

On Tuesday 18 November 2003 05:52, John Szakmeister wrote:
> Oof, found a problem with this... the svn:executable property doesn't get
> applied. I've got to track down how to do that now.

Okay, I fixed this problem, but it brought around more questions, that I feel
I need a little guidance on.

The next problem I ran into was time-stamping the file. In an export from the
repository, you'd get the last committed time stamps. So, I did the same for
export... except for one problem, what do I do with locally modified files?
At the moment, I'm making a call to svn_wc_status() and checking text_status
or props_status != normal. If either has been modified, then I'm pulling the
time stamp from the WC file and applying it to the export.

Then I started thinking, that if I copied the modified file times from the
working copy, that someone might use that information to determine what had
changed. Then I got to wondering whether or not the $LastChangedRev$ should
reflect the fact that a file is locally modified (perhaps something like
$LastChangedRev: 2+ $), as well as changing $LastChangedBy$ to reflect the
current user.

So now, I'm a bit confused as to what I should do. :-) I want this to do the
intuitive thing, but I'm not sure what that is. Any help that can be offered
would be appreciated.


To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Tue Nov 18 13:05:49 2003

This is an archived mail posted to the Subversion Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.