Thanks Niko, Mark, Maciek.
I was a little confused because I was reading the 'last changed
revision' of trunk, which I now understand is independent from the
global (repository) revision. I think I read that this is the same for
'modules', i.e., if you have two modules under one repository, project
#1 having 5 'real' revisions, and project #2 having 5 trillion :-), you
could also export revision # 4 trillion (for example) from project #1
(even though it hasn't been updated ... forever). Is that correct? Kinda
odd that. I guess you could correct that by just having separate
repositories?
Not only was the cancelled export not cleaned up, it didn't even appear
to be stopped. Is this an API limitation (I'm using the default --
JavaHL). One would think that it was a basic feature.
Also, I noticed there was no progress information while exporting ...
another limitation?
Glen.
Maciek Sakrejda wrote:
> 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
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subclipse.tigris.org
For additional commands, e-mail: users-help@subclipse.tigris.org
Received on Mon Dec 17 18:14:05 2007