Re: [stellation-res] Checkin of new files.

["Mark C. Chu-Carroll" <mcc@xxxxxxxxxxxxxx>]

On Saturday 24 August 2002 04:04 pm, Jonathan Gossage wrote:
>
> As I have discovered since my post the files were disappearing as a result
> of a problem in the TextArtifact.normalize() method. However some
> organizations like to work in a mode where local copies of files are not
> permitted unless the files are explicitly checked out. In this case, an
> option to delete the workspace copy makes sense.

One of the great plagues of SCM work is the utter lack of standard
terminology.

Creating a workspace from a project version is called anything from
"checkout" to "populate" to "view". Moving changes from a workspace
to the repository is called anything from "checkin" to "commit" to 
"update". Merging from the main branch is called anything from "merge"
to "update" to "rebase". It's frustrating.

For some systems, checkout means "create locally accessible copy". For others 
(for example ClearCase) it means something akin to "create locally accessible 
editable copy".  For some, checkout is a project-level verb; for others, it's 
a file or directory-level verb.

In Stellation, checkout is a project-level operation that creates a local 
image of a project version stored in the repository. Checkout is strictly 
full-project, never individual file. Eventually, we will provide heirarchical
sub-projects, so you'll be able to checkout defined subparts of a system;
and we will support locking if you want it (with the lock command called 
"lock").

	-Mark

-- 
Mark Craig Chu-Carroll,  IBM T.J. Watson Research Center  
*** The Stellation project: Advanced SCM for Collaboration
***		http://www.eclipse.org/stellation
*** Work Email: mcc@xxxxxxxxxxxxxx  ------- Personal Email: markcc@xxxxxxxxxxx