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

status command ignores property changes in repository

From: Tom Karzes <tkarzes_at_pixelworks.com>
Date: 2006-11-14 00:09:04 CET

As far as I can tell, "svn status --show-updates" ignores properties that
have changed in the repository. This means that there's no way to use
"svn status" to tell if your working copy is truly up-to-date. Some
reasons why I believe this is a bug/design flaw:

    1. Since "svn status" does report changed properties in your working
        copy, it is inconsistent for "svn status --show-updates" not to
        report changed properties in the repository.

    2. There is no simple passive way to know if your working copy is
        up-to-date, i.e. if "svn update" would update anything. You
        could probably do a recursive "svn info" on the repository URL,
        and compare each and every "last changed revision" to see if
        everything is up-to-date, but this seems impractical to me.

    3. If you make some unrelated change to your working copy, and
        try to commit it, the Subversion server will complain that your
        working copy is out-of-date. If your working copy is out of
        date to a point where you cannot commit changes made to it,
        then "svn status --show-updates" needs to report that.

Am I missing something here? Or is this just a bug/design flaw in
the status command?

Tom Karzes
tkarzes@pixelworks.com

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Nov 14 17:20:18 2006

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.