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.
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.
If there are no objections, then I'll commit this in a day or two. BTW, I've
also got some new export tests for this new functionality. I'll look at the
help strings for export too. If anyone has any suggestions, I'd appreciate
it!
-John
Log:
-------------------------------------------
Fixes a minor issue with the 'export' command failing to copy the BASE
revision of files when '-rBASE' is specified. Also fixes translation of
keywords for locally modified files.
* subversion/libsvn_client/export.c
(copy_versioned_files): Added revision parameter. Changed the copy
algorithm to translate keywords and eol style when appropriate.
(svn_client_export): Added the ability to better distinguish when the
repository should be contacted versus using the local base or working copy.
-------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 16 18:45:28 2003