You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Bill Comisky <bc...@pobox.com> on 2003/12/12 23:15:50 UTC
problem with 'svn st' on external directory
I have a repository with several project subdirectories. project2
contains some svn:external references to subdirectories of project1. I
have a working copy for each project (WC1 and WC2 respectively).
I just experienced some strange behaviour with 'svn st' while working in
one of the external directories in WC2. Basically 'svn st' returned no
output, as if WC2 was up to date. The problem is that I had made few
revisions from WC1 and committed them.
Within WC1 of repo1:
[bcomisky@twain @hfss]$ svn info pswopTestOutput.m
Path: pswopTestOutput.m
Name: pswopTestOutput.m
URL: http://xxxxx.com/svn/path-to-project1/@hfss/pswopTestOutput.m
Repository UUID: 560c3632-cac0-0310-8450-99abee840cfb
Revision: 239
Node Kind: file
Schedule: normal
Last Changed Author: bcomisky
Last Changed Rev: 239
Last Changed Date: 2003-12-12 13:05:55 -0600 (Fri, 12 Dec 2003)
Text Last Updated: 2003-12-12 12:51:59 -0600 (Fri, 12 Dec 2003)
Properties Last Updated: 2003-11-03 19:40:17 -0600 (Mon, 03 Nov 2003)
Checksum: c638928c8ee16ab01e1cc54a0bcc03a6
Within the project1 external subdirectory of WC2:
[bcomisky@twain @hfss]$ svn st
[bcomisky@twain @hfss]$ svn info pswopTestOutput.m
Path: pswopTestOutput.m
Name: pswopTestOutput.m
URL: http://xxxxx.com/svn/path-to-project1/@hfss/pswopTestOutput.m
Repository UUID: 560c3632-cac0-0310-8450-99abee840cfb
Revision: 236
Node Kind: file
Schedule: normal
Last Changed Author: bcomisky
Last Changed Rev: 223
Last Changed Date: 2003-12-10 13:49:36 -0600 (Wed, 10 Dec 2003)
Text Last Updated: 2003-12-10 13:50:27 -0600 (Wed, 10 Dec 2003)
Properties Last Updated: 2003-12-10 13:50:27 -0600 (Wed, 10 Dec 2003)
Checksum: 61663bc0902006414b876c6770b4b0b4
[bcomisky@twain @hfss]$ svn up
U pswopTestOutput.m
Updated to revision 239.
You can that 'svn up' updated to HEAD but 'svn st' didn't show anything
beforehand. Is there a way I could have corrupted the repository or the
WC? Or should I just 'svn up' and forget it?
bill
--
Bill Comisky
bcomisky@pobox.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: problem with 'svn st' on external directory
Posted by Dominic Anello <da...@danky.com>.
On 2003-12-12 17:15:50 -0600, Bill Comisky wrote:
----8<----
> Within the project1 external subdirectory of WC2:
>
> [bcomisky@twain @hfss]$ svn st
----8<----
> [bcomisky@twain @hfss]$ svn up
> U pswopTestOutput.m
> Updated to revision 239.
>
> You can that 'svn up' updated to HEAD but 'svn st' didn't show anything
> beforehand. Is there a way I could have corrupted the repository or the
> WC? Or should I just 'svn up' and forget it?
>
> bill
Bill,
By default, svn st only shows you files that have been locally modified
since your last commit. It will not show you files that have been
modified in a revision newer than your current working copy.
To see files that are updated in the repository but not modified
locally, use:
svn st -u
this will show you all the files that will get modified if you were to
do an update as well as changes you've not committed.
-Dominic
Re: problem with 'svn st' on external directory
Posted by Erik Huelsmann <e....@gmx.net>.
> [bcomisky@twain @hfss]$ svn up
> U pswopTestOutput.m
> Updated to revision 239.
>
> You can that 'svn up' updated to HEAD but 'svn st' didn't show anything
> beforehand. Is there a way I could have corrupted the repository or the
> WC? Or should I just 'svn up' and forget it?
Using
$ svn st -u
you can see what happened locally and in the repository. 'svn st' does not
normally check the repository status of your resources.
HTH,
Erik.
--
+++ GMX - die erste Adresse für Mail, Message, More +++
Neu: Preissenkung für MMS und FreeMMS! http://www.gmx.net
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: problem with 'svn st' on external directory
Posted by Bill Comisky <bc...@pobox.com>.
duh! Please ignore previous posts, I was just forgetting the '-u' switch.
(me very tired).
bill
--
Bill Comisky
bcomisky@pobox.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Re: problem with 'svn st' on external directory
Posted by Bill Comisky <bc...@pobox.com>.
Just made another commit to project1 and 'svn st' in WC2 does not show
anything for the external reference.. I know this used to work. I'm kind
of busy at the moment, but if I have a minute, I'll try to reproduce on a
fresh checkout, different repo, etc.
Forgot to mention, I'm using:
[bcomisky@twain trunk]$ svn --version
svn, version 0.34.0 (dev build)
compiled Dec 5 2003, 00:17:05
This was built from r7936 for both svn client and server.
bill
On Fri, 12 Dec 2003, Bill Comisky wrote:
> I have a repository with several project subdirectories. project2
> contains some svn:external references to subdirectories of project1. I
> have a working copy for each project (WC1 and WC2 respectively).
>
> I just experienced some strange behaviour with 'svn st' while working in
> one of the external directories in WC2. Basically 'svn st' returned no
> output, as if WC2 was up to date. The problem is that I had made few
> revisions from WC1 and committed them.
[ snip ]
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org