Mark, thank you very much for your suggestion. Just for completeness, if anyone's reading this in the archives, I pasted in my session below. Thanks also for the explanation of what was happening. I'm looking forward to using Subversion more as I better understand it.
-Kevin
========================
kevinz@www:~/public_html/orderDB$ svn status
A + scripts
D obsolete
D obsolete/loadKeywords.pl
D obsolete/loadInventory.pl
D obsolete/buildOrderDB.pl
kevinz@www:~/public_html/orderDB$ svn update
At revision 20.
kevinz@www:~/public_html/orderDB$ svn commit -m"Renamed obsolete/ to scripts/."
Deleting obsolete
Adding scripts
Adding scripts/buildOrderDB.pl
Adding scripts/loadInventory.pl
Adding scripts/loadKeywords.pl
Committed revision 21.
kevinz@www:~/public_html/orderDB$
=============================
>>> Mark Phippard <MarkP@softlanding.com> 03/28/05 04:34PM >>>
KEVIN ZEMBOWER <KZEMBOWE@jhuccp.org> wrote on 03/28/2005 04:27:25 PM:
>
> Please let me know if this is a bug that I should report. Or, if not a
bug,
> what should I do to commit the changes?
You need to run svn up before you can commit again.
This is the "mixed revision working copy" issue that bites so many people.
When you did the commit of the change to the file in obsolete, that
caused the obsolete folder to become out of date. Commit does not update
the revision for the folder in your WC, just the file in the folder.
Running svn up will get the folder up to the latest revision which is
required to move it, delete it or modify its properties.
Mark
_____________________________________________________________________________
Scanned for SoftLanding Systems, Inc. by IBM Email Security Management Services powered by MessageLabs.
_____________________________________________________________________________
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Tue Mar 29 16:33:59 2005