On Wed, Mar 23, 2011 at 1:43 PM, <skip at pobox.com> wrote: > > Nick> 7. Merge the heads on the oldest branch that now has multiple heads > > Two more stupid questions: > > 1. Don't all branches have multiple heads? Every time I execute hg heads I > see many. The branches we mainly care about should generally only have 1 head in the public repository (the tip for the default branch, the last merge point to default for 3.2 and 2.7, the last merge point to 3.2 for 3.1). > 2. Oldest in what way? Pythonically (2.6 is older than 2.7 though it might > have more recent checkins) or revision-wise (rev 68001 is newer than > 68000)? Oldest in terms of the bug fix merging workflow (i.e. 3.1->3.2->default, or 2.6->2.7 if you're actually updating more than just 2.7 in the 2.x series) Cheers, Nick. -- Nick Coghlan | ncoghlan at gmail.com | Brisbane, Australia
RetroSearch is an open source project built by @garambo | Open a GitHub Issue
Search and Browse the WWW like it's 1997 | Search results from DuckDuckGo
HTML:
3.2
| Encoding:
UTF-8
| Version:
0.7.4