What you are seeing is the correct behavior. This is called "Mixed
Revision Working Copies" If I remember correctly.
What this means is that the repository is on r1000 but main/sub1 hasn't
been committed to since r900
likewise with main/sub2/sub2a not being committed since r666
Make sense?
Frescard wrote:
> So far I've been using TortoiseSVN, and I just installed Subversion (V
> 1.5.2) to automate some jobs via batch files.
>
> Everything works ok, but there seems to be a problem updating subfolders.
>
> When I look at the log files of a subfolder I get the correct revision
> number.
> When I try to update this folder though, it gives me the revision number of
> the mother folder.
> The effect is the same if I first change directory to the respective path,
> and then issue a simple "svn update", or whether I supply a path with the
> update command.
>
> Here is an example.
> No matter which folder I'm in (sub1,sub2,sub2a or sub3) I will always get
> the message "At revision 1000" when doing a "svn update".
> If I do a "svn log" I will get the correct revisions for the specific
> folders though.
>
>
> main (rev. 1000)
> |--- sub1 (rev. 900)
> |--- sub2 (rev. 700)
> |--- sub2a (rev. 666)
> |--- sub3 (rev. 800)
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
> For additional commands, e-mail: users-help_at_subversion.tigris.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-09-05 20:02:36 CEST