On Saturday 08 November 2003 21:42, kfogel@collab.net wrote:
[snip]
> Those sound good; I can't think of anything else off the top of my
> head... Oh: maybe, exports that include eol translation and/or keyword
> substitution?
That was actually a great idea, it seems to have brought up a couple of
issues. Let's say I modify my working copy so that A/mu now has a property
set on it (svn:eol-style) and I've appended new text to it. If I export the
working copy, should I see the new property I set get applied? I ask,
because right now if I export a working copy that has modified properties
(but not committed), I don't see the new properties applied in the export
operation. The documentation for export says "All local changes will be
preserved, but files not under revision control will not be copied." Well,
technically setting a property but not committing it is a local change, and
I'm not seeing it get exported.
So what's the right behavior here? Should export be applying these new
properties? If not, then should we update the documentation to reflect this
fact? If export should be applying these properties, should I open an issue?
As a side note, I've added 5 new tests in r7680. Once we work out the correct
behavior of export with local property changes, I'll put in several more
tests to ensure that it does what is expected in those cases.
-John
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org
Received on Sun Nov 9 15:59:08 2003