On Feb 26, 2011, at 06:32 PM, Éric Araujo wrote: >>> Named branches are exclusive, they can't be a subset of each other ;) > >Actually, they can. Take the example of the Mercurial repo itself. They >fix bugs in the stable branch and add features in default. When they >merge stable into default and commit, default becomes a superset of >stable. That is to say, someone pulling default also gets the >changesets from stable that are ancestors of the merge changset. Or in >other words, if you check out default, you get all bug fixes from stable. That makes sense, but correct me if I'm wrong, it's the 'merge' operation that made this happen, right? A merge essentially brings the changesets from one branch into another. -Barry -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 836 bytes Desc: not available URL: <http://mail.python.org/pipermail/python-dev/attachments/20110226/5ef57450/attachment.pgp>
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