Re: [tlug] silly question on subversion

[Curt Sampson <cjs@example.com>]

On 2008-05-02 17:17 +0900 (Fri), Gernot Hassenpflug wrote:

> I repeat the above for project2, but when I check it out, I get
> revision 2 ! Any change I make to *either* of project1 or project2
> increments the revision number for whichever one I check out.

Correct. You asked for the latest revision from the repository, so it
gave you that. Of course, there might be no changes in your particular
subtree of the repository. That's nothing to worry about.

If your checkout were of the full repo (i.e., from the root directory
above your individual project directories) you would see a change for
every revision increment.

It would, I suppose, be possible to say

On 2008-05-02 17:58 +0900 (Fri), Mike Mazur wrote:

> This also took a little getting used to when I first tried Subversion.
> I'm not sure the detailed decision process or rationale behind this
> design decision....

Well, consider the alternative. I'm at revision 100, and I ask to update
my subtree to HEAD, which is revision 110. So svn looks, and sees that
on my branch there are no changes between 100 and 100. So does it leave
it at 100? When I come back later and look at it, and I know that head
is 110, how do I know if this is at head or not? I have to look manually
to see that there are no changes between 100 and 110 on this subtree.

The alternative, of course, is to update it, but that might leave me with
a huge pile of conflicts to resolve if I had changes in my checkout, which
is inconvenient.

One way to understand these types of design decisions is to consider
a different way of doing it, and go through all the details of doing
it that way. This may or may not resolve your question about why they
did it a certain way, but is likely at least to give you a better
understanding of the system you're using.

cjs
-- 
Curt Sampson       <cjs@example.com>        +81 90 7737 2974   
Mobile sites and software consulting: http://www.starling-software.com