... a version control system might be ultra-minimal and not offer features like branching, tagging, differencing, and merging, etc.. It might only offer manual roll-back of a specific block to a prior state, or possibly a grand snapshot of all blocks captured at a particular point in time. Whatever-- I'm just looking for past strategies. If I *had* to do it, I would keep a looseleaf printed copy of screens and keep track of dates. ...

... and forge ahead. Then the pattern can repeat with A and C (assuming A is the project leader) etc. In my experience, this is a very common scenario. We've seen remarkably little need to recover snapshots from the past, even though we've used CVS for some years now. But the kind of auditing facilities that this Audit utility then and Beyond Compare now provide are invaluable in multi-programmer projects. Cheers, Elizabeth --...

... control system might be ultra-minimal and not offer features like branching, tagging, differencing, and merging, etc.. It might only offer manual roll-back of a specific block to a prior state, or possibly a grand snapshot of all blocks captured at a particular point in time. Whatever-- I'm just looking for past strategies. Sorry, I can't give you *existing* strategies because we don't use blocks any more, but I can ...

John Passaniti wrote: John Doty wrote: I'm not sure what your real requirement is: you need to function entirely within a block world? When we did that we just made a floppy with a snapshot whenever we would have made a commit. Wound up with boxes of labeled, dated floppies. Start a new fork, start a new box ;-). I suppose you could do the same with CD's. Cheap and simple enough... I didn't want to discuss ...

John Doty wrote: I'm not sure what your real requirement is: you need to function entirely within a block world? When we did that we just made a floppy with a snapshot whenever we would have made a commit. Wound up with boxes of labeled, dated floppies. Start a new fork, start a new box ;-). I suppose you could do the same with CD's. Cheap and simple enough... I didn't want to discuss my application because it doesn't matter...

... etc.. It might only offer manual roll-back of a specific block to a prior state, or possibly a grand snapshot of all blocks captured at a particular point in time. Whatever-- I'm just looking for past strategies. ...: you need to function entirely within a block world? When we did that we just made a floppy with a snapshot whenever we would have made a commit. Wound up with boxes of labeled, dated floppies. Start a new fork, ...

... offer manual roll-back of a specific block to a prior state, or possibly a grand snapshot of all blocks captured at a particular point in time.  Whatever-- I'm just ... In any case, modern versioning tools usually store the deltas of the modification instead of a full snapshot of the file. A full snapshot could otherwise be too space consuming. A version number is associated to each delta and the extraction of a "version" involves ...

...control system might be ultra-minimal and not offer features like branching, tagging, differencing, and merging, etc..  It might only offer manual roll-back of a specific block to a prior state, or possibly a grand snapshot of all blocks captured at a particular point in time.  Whatever-- I'm just looking for past strategies. Are you looking for past strategies or current strategies (or both)? You context seems to imply you're ...

...answer in that case would be to version control the files holding blocks. I appreciate that such a version control system might be ultra-minimal and not offer features like branching, tagging, differencing, and merging, etc.. It might only offer manual roll-back of a specific block to a prior state, or possibly a grand snapshot of all blocks captured at a particular point in time. Whatever-- I'm just looking for past strategies.

...Use of uninitialized value in subroutine entry at t/08-filter.t line 16. ok t/09-error.................skipped: no network device available t/10-fileno................skipped: no network device available t/11-snapshot..............skipped: must be run as root t/12-next..................skipped: pcap_next() behaves too strangely for being tested on random machines t/13-dispatch..............skipped: must be run as root t/14-datalink...