A RetroSearch Logo

Home - News ( United States | United Kingdom | Italy | Germany ) - Football scores

Search Query:

Showing content from https://mail.python.org/pipermail/python-dev/2014-March/133216.html below:

[Python-Dev] hg branching + log question

[Python-Dev] hg branching + log questionBenjamin Peterson benjamin at python.org
Mon Mar 17 21:04:11 CET 2014
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.
More information about the Python-Dev mailing list

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