On 02 Mar 2012, at 01:52, Chris Cunningham wrote: > The issue is that Monticello is setup for distributed processing, and > allowing for multiple repositories, some of which may not be available > to all of the users for a project. For instance, a project might be > developed internally (or on the developers hard-drive) until they feel > comfortable distributing the code later. So, publicly, you get > version 12, 17, 34, and 37. There is no access to the intermediate > ones (unless you happen to be the one that created them and didn't > release them). The 'whole ancestry' let's you do diffs off of a > version derived from 37 against one derived from 34 - the ancestry can > determine that version 34 if 'common', and work from there. [Note > that just numbers aren't enough - the original developer, say, cbc > could have version cbc.34, while you could have, say, CamilloBruni.34, > but yours is based off of 17 (since you picked up that verison and > started working there). So, merging cbc.37 with CamilloBruni.34 would > need to pull down cbc.17 for a good merge to work.] > > At least, that's my understanding from long ago discussions.
This makes sense, but how is this handled with git ? Sven
smime.p7s
Description: S/MIME cryptographic signature
