bug? Directory version doesn't update on commit

[Karl Chen <qu...@hkn.eecs.berkeley.edu>]

Hi svn developers,

If I do 'svn ci' in a directory to check in recursively, the
version of the directory (i.e. from 'svn info') doesn't update
until I do 'svn update'.  Is this a bug (and if not why not)?


-- 
Karl Chen 2003-11-05 12:01

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: bug? Directory version doesn't update on commit

[Chia-liang Kao <cl...@clkao.org>]

There could be an optmization which I also planned in svk. After the
commit is done, we check if there's other changes between the revision
of the parent directory and the new revision. If not, we could simply
make the while directory single revision.

This is likely the case if the repository is only accessed by a single
person, and would decrease the need for constructing mixed-revision
trasaction root for further operations.

Cheers,
CLK

On Thu, 2003-11-06 at 04:37, Ben Collins-Sussman wrote:
> It's not a bug.  Remember that directories are versioned objects just
> like files.  The directory wasn't committed, because it had no changes. 
> Some of its children were ocmmitted, though.  Ergo, the children are now
> at HEAD revision, but the parent directory is not.  You have a
> mixed-revision working copy, which is pretty common.  "svn update"
> brings the whole working copy to a single revision.


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org

Re: bug? Directory version doesn't update on commit

[Ben Collins-Sussman <su...@collab.net>]

On Wed, 2003-11-05 at 14:04, Karl Chen wrote:
> Hi svn developers,
> 
> If I do 'svn ci' in a directory to check in recursively, the
> version of the directory (i.e. from 'svn info') doesn't update
> until I do 'svn update'.  Is this a bug (and if not why not)?

It's not a bug.  Remember that directories are versioned objects just
like files.  The directory wasn't committed, because it had no changes. 
Some of its children were ocmmitted, though.  Ergo, the children are now
at HEAD revision, but the parent directory is not.  You have a
mixed-revision working copy, which is pretty common.  "svn update"
brings the whole working copy to a single revision.

If the parent directory had a propchange attached to it, then 'svn
commit dir' would indeed have committed the parent directory itself,
along with any modified chidren, and the parent directory would also be
at HEAD.

Just remember that 'svn commit dir' means "search for any changes within
dir, and commit them."  The directory itself may be one of the changed
items, or it may not.  Usually not.



---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@subversion.tigris.org
For additional commands, e-mail: dev-help@subversion.tigris.org