Hello folks:
I've talked with xfury, and I think we need to organize /trunk a little
better.
If you have changes in your local working copy, your SVN client will require
an "svn update" on your working copy before you can commit your changes,
after the changes I am doing are complete.
As I am not sure as to how politely SVN will understand the restructuring,
you should make a backup copy of your local working copy, in case your
changes won't merge into the trunk. In such case, the trunk can be reverted
to its current revision number, 245, and then you can commit your changes,
and then we can try /trunk restructuring again. But I seriously doubt it
will be a problem.
The only hindrance subversion creates, is that every single directory
relocation has to be done in its own revision. After all this is done, and I
have corrected the NAnt build files, I will send out another notification.
-Bruce
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
SharpOS-Developers mailing list
SharpOS-Developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/sharpos-developers
