Timeline for Version control management of large projects
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 29, 2011 at 10:36 | comment | added | Mark Booth | @Andrea, quant_dev is right, even though Mercurial is a DVCS you still shouldn't end up with two heads. To get two heads the pusher has to explicitly force it to accept the new head. | |
| Apr 29, 2011 at 8:55 | comment | added | reinierpost | You can impose a hierarchy by policy. That's how it works for the Linux kernel, apparently. | |
| Apr 29, 2011 at 8:46 | comment | added | Andrea | Mercurial, unlike SVN, is not centralized. So there is not really any hierarchy like the one you describe. Appearance of heads is the rule in Mercurial, and merging of two branches is rather painless. I was wondering what happens in a more complex situation, though. | |
| Apr 29, 2011 at 8:42 | history | answered | quant_dev | CC BY-SA 3.0 |