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

Re: [PATCH] Modified export behavior

From: Julian Foad <julianfoad_at_btopenworld.com>
Date: 2003-11-17 19:05:47 CET

John Szakmeister wrote:
> Okay, I've went and modified the export behavior to do a couple of things now:
>
> 1) Now translates keywords when doing an export of a working copy.
>
> 2) Make better use of -r REV and a working copy path. You can now specify
> -rBASE on the command line and export will translate and copy the text base
> instead of the working copy files which may have been modified.
>
> 3) In the case that -r REV can't be satisfied by the working copy path (i.e.,
> PREV), then we'll contact the repository to satisfy the request.

That all sounds good.

> For the keyword translation of the locally modified working copy, I used the
> new properties on the file, but things like $LastChangedBy$ and
> $LastChangedRev$ fall back to using the values associated with the commit.

You mean, when you export from WC (not from BASE), the keywords that refer to "this revision" will take their values from the BASE revision, because there is no "this revision" yet? That sounds like a reasonable behaviour, but I just want to ask whether that situation arises with any other commands and, if so, do they handle it the same way?

(The only one I can think of is "svn cat -rWC" which is not yet implemented, for which there is a patch attached to issue 1361: svn cat -rBASE contacts repository. I can't remember what it does in this situation, but it can be changed to match your choice.)

- Julian

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Mon Nov 17 19:05:46 2003

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