Re: Missing log info (WAS: getting a repository's latest revisio n)

On Tue, 12 Oct 2004, Scott Palmer wrote:

> > Confusingly, your WC root is now _still_ at revision 112. This semingly
> > odd behaviour is explained by the fact that if, say, someone else had
> > got
> > in before you, and committed a r113 that added files to the root, then
> > after your commit you wouldn't have those (added) files in your WC - so
> > the root stays at 112 to remember that there may be things it needs to
> > pick up. In this case that isn't necessary, but it would be
> > inconsistent
> > for the behaviour to change in this case.
>
> I thought subversion would not allow the commit unless I did an update
> in that case? I.e. if my WC is at 112, someone else commits 113, then I
> try to commit, doesn't subversion complain that my BASE is out of date?

It allows the commit provided that no files or directories that you're
committing have changed in the intervening revisions (since this would
necessitate a merge). Changing the properties on a directory counts as
modifying the directory, but modifying files underneath it doesn't.

I hope that clears everything up :)

Patrick

-- 
The easy way to type accents in Windows: http://www.frkeys.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org