Glen,
This sounds like the correct behavior. Subversion versions the entire
repository, so when you commit to a branch, you create a "new revision"
of the trunk as well. Subversion is smart about how this is managed and
doesn't actually create a new copy of the trunk, but in all ways, this
new revision of trunk is valid. When you check out that revision of
trunk, Subclipse is just doing what you asked it to: checking out trunk
at that revision.
As far as lack of cleanup on cancel: that would be nice, but
command-line svn behaves the same way, so it's probably an API issue.
-Maciek
On Mon, 2007-12-17 at 18:03 +0200, Glen wrote:
> Hi,
>
> I'm new to SVN, and I wanted to see what would happen if I attempted to
> export a non-existent revision from trunk (a revision which was however
> available in branches).
>
> Result: The whole of trunk (I assume the head revision) was exported.
>
> Expected: An error message to be displayed mentioning that the revision
> does not yet exist.
>
> Is this what it supposed to happen?
>
> On a related note, when I clicked 'Cancel', the download seemed to
> continue to the end (and not clean up either) (I read about this
> happening in older versions with the checkout and sync operations).
>
> Thanks,
>
> Glen.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
> For additional commands, e-mail: users-help@subclipse.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Dec 17 17:16:48 2007