[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
[stellation-res] Modified Workspace
|
During the MySql testing I ran the following sequence of commands from the
tutorial.
Start with the workspace containing branch 1.0 checked in.
Run the following sequence of commands:
svc --revision 1.0 checkout demo
svc fork exact
The modify the contents of one of the files in the workspace.
Now run the command:
svc checkin
At this point the new branch "exact" should contain one modified file.
Now prepare to create a second branch with the following command.
svc --revision 1.0 checkout demo
As I understand it this should checkout the base branch 1.0 into the current
workspace. However, even though the previous contents of the workspace have
just been checked in I get the following warning from Stellation:
This workspace already contains a project with modified content.
You must use --force if this is really what you want.
I would have thought that the previous checkin would have left the workspace
in an unmodified state. Is the observed behaviour correct? I am a little
reluctant to force on with further testing if the system has beenplaced into
an incorrect state.
Regards
Jonathan Gossage
Personal Email
jgossage@xxxxxxxx
Business Email
jonathan@xxxxxxxxxxxxxx