|
Size: 1207
Comment:
|
Size: 346
Comment:
|
| Deletions are marked like this. | Additions are marked like this. |
| Line 1: | Line 1: |
| Some rant about general VCS requirements which will ''ideally'' end in a formal model matching mercurial implementation (with hope it's not totally out of topic on the mercurial wiki). See this page as a pure intellectual exercise for now. = Requirements = Express from coarser detail to finer detail. == High level requirements == * Manage objects (will be files, directory, metadata...) * add object * remove object * modify object * keep immutable history (except for obliterating some content ?) * restore state from the past == Intermediate level requirements == * keep trace of who did the object management actions * add property to objects (comment, date, author..) * add property to history state (tags ?) == Distributed requirements == * Local history (will end in repository / branches) * clone * merge == Other secondary requirements == * narrow/shallow cloning ? == Low levels requirements == Map to mercurial commands/functions: * init, add, remove, backout, branch, clone, commit, copy, move, merge, push, pull, revert, tag Map to mercurial internals: * manifest, revlogs, = Formal Method = * B event (via rodin platform) |
The person who wrote the report is called Darren Rippey.<<BR>> For years he is been living in Texas but his wife actually them to move. Playing lacross is the text his family and to him enjoy. Filing has been his holiday job for a while they are. Go to his website to find out more: http://socialexchangelist.com/index.php?a=stats&u=marisachan |
The person who wrote the report is called Darren Rippey.
For years he is been living in Texas but his wife actually them to move. Playing lacross is the text his family and to him enjoy. Filing has been his holiday job for a while they are. Go to his website to find out more: http://socialexchangelist.com/index.php?a=stats&u=marisachan