Timeline for Do large mercurial repositories suffer from a "push race"?
Current License: CC BY-SA 3.0
6 events
when toggle format | what | by | license | comment | |
---|---|---|---|---|---|
Jun 10, 2011 at 3:18 | vote | accept | TheLQ | ||
Jun 7, 2011 at 7:43 | comment | added | Ed James | Like I said, most of the time everyone is working on their own branch (you're very unlikely to be working on exactly the same issue as another person), so while everyone does push at the end of the day it's to different branches. Plus, at my work we have flex time so it's more of a 4pm-6pm rush ;) | |
Jun 6, 2011 at 21:23 | comment | added | Cem Catikkas | How come there is no 5pm push rush? | |
Jun 6, 2011 at 9:26 | comment | added | Ed James | That's the thing, as far as mercurial is concerned a clone is a branch, you can still do pretty much everything you can do with a standard "head" (and some more stuff!), but you have the added luxury of the pull/push level of distance from the trunk. I'm not sure what you mean about permanence, when you're done with your clone you can just delete it. | |
Jun 6, 2011 at 3:17 | comment | added | TheLQ | I've always heard that you clone to work on experimental features, not branch. Most of the reasons I heard is that in mercurial branches are much more permanent than in Git. I could be wrong however | |
Jun 5, 2011 at 22:00 | history | answered | Ed James | CC BY-SA 3.0 |