| How does Stellation store revisions? [message #584979] |
Fri, 18 October 2002 20:12 |
Eclipse User |
|
|
|
Originally posted by: wlandry.ucsd.edu
Greetings,
I'm a developer for Arch[1], so I've been looking how other SCM's
implement things. I've read many of the documents on the web, but I still
don't completely understand some of the internals of Stellation. I'd
appreciate it if someone could enlighten me.
1) As I understand it, Stellation's eventual plan is to break code up into
parts based on the syntax of the language, and then do revision management
on those parts. Right now, it only operates on files. Does that mean
that I could use it right now for contents which are difficult or
impossible to parse?
2) I assume that somewhere in the database is a complete copy of some
revision of a file. Different revisions are then created by applying
patches.
a) Does that mean that whenever you run Stellation, all of the
revision + patches are loaded into memory?
b) Which revision do you store? The first revision, the last active
revision, the last revision for each branch, or something completely
different?
3) It seems that when you commit changes, you don't have to explicitly
tell Stellation which files you edited. That is, you didn't have to check
out a file for editing before editing it. Does that mean that Stellation
does a recursive diff to find out what changed?
4) Is it possible to set up a public, read-only repository? If so, does
it use the normal authentication mechanism (so you have to set up a
special user with read-only priviledges), or does it bypass it entirely?
Thanks,
Walter Landry
wlandry@ucsd.edu
[1] http://www.fifthvision.net/Arch
|
|
|
Powered by
FUDForum. Page generated in 0.02981 seconds
] 
Search
Help
Register
Login
Home
