[Python-Dev] hg branching + log question
Benjamin Peterson
benjamin at python.org
Mon Mar 17 21:04:11 CET 2014
More information about the Python-Dev mailing list
Mon Mar 17 21:04:11 CET 2014
- Previous message: [Python-Dev] hg branching + log question
- Next message: [Python-Dev] hg branching + log question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
On Mon, Mar 17, 2014, at 13:02, Sean Felipe Wolfe wrote: > I'm getting my feet wet with the cpython sources and Mercurial. I'm a > bit confused -- when I checkout a branch, eg. 3.3, and I do an 'hg > log', why do I see log messages for other branches? That's just the way Mercurial works. If you only want to see messages on the current branch, do "hg log -b .". > > I'm expecting different branches to be kept discreetly. If I switch to > 3.3, then I expect to see only 3.3 commits and changes. > > Also, what does the branch 'default' mean in this context? Since > cpython is concerned with 3 major concurrent release tracks, why would > there even be a default ? Does it just point to 3.4? It's what will become 3.5 as of today.
- Previous message: [Python-Dev] hg branching + log question
- Next message: [Python-Dev] hg branching + log question
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list