Monticello and Changesets
Last updated at 12:24 pm UTC on 17 January 2006
What are these MCx changesets?
Every time that MC makes a change, it opens a new, sequentially numbered,
change set. So each of the MCx changesets represents a separate Monticello
operation.
MC largely ignores changesets but tries to be polite about not stomping on them. So it sticks everything it does into numbered MC changesets and then forgets about them.
Can a normal changeset preamble/postscript be used for the fileout in the Version?
No, not really - or at least, MC would have to be extended to know about this and deal with them properly when it parses/merges/etc the definitions in the fileout. I use class side #initialize methods to do postscript-type stuff, which seems to work ok.
