[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: svn log questions

From: <trlists_at_clayst.com>
Date: 2004-12-10 18:05:09 CET

On 10 Dec 2004 Ben Collins-Sussman wrote:

> After the commit is done, your working copy of foo.c is at r6, but the
> entire rest of your working copy (including the parent dir of foo.c) is
> still at r5. (Most people don't realize that after *every* commit,
> they have a mixed-revision working copy!)

Good point. I sure didn't!

I think the docs are confusing on this. The section on "The
Limitations of Mixed Revisions", which I had read a couple of times,
makes it sound like it's a bit out of the ordinary to have mixed
revisions. It may be odd in the world of VCS's generally, but for
Subversion it is probably the normal state of a WC and that would be
worth mentioning. It is described as a "special flexibilty" and not as
the routine condition.

> When you run 'svn subcommand' with no arguments, it means, "run the
> subcommand on a default target of CWD at its working revision". This
> is the general rule.

The issue then is the definition of "working revision". I would have
called the "working revision" r6 in your example, but I see it can be
defined either way.

What switch (if there is one) means "run the subcommand on a default
target of CWD at the most recent revision which has a committed change
to CWD"?

What exactly is getting updated when you do an svn update and nothing
has actually changed except the single file you just committed? Is it
just the revision number in .svn/entries?


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Dec 10 18:07:50 2004

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.