Le 18/03/2014 04:05, Jeff Allen a écrit :
I found it helpful to practice extensively on something that doesn't
matter. The gap for me is still examples of what I want "done well".
Clearly the Python repos represent complex work, but even accepting it
is all done well, are without much commentary.
I have also found hg difficult to get to grips with from cold (but I
like it). The hg command and its help are good, as Antoine says, but if
I'm doing something complex, the visualisation of the change sets that
TortoiseHG provides is invaluable (and of other invisible structures,
such as the M
Ah well, ok. That seems pretty counterintuitive to me though. I
suppose Hg has its quirks just like ... that other DCVS system ... :P
On Mon, Mar 17, 2014 at 1:07 PM, Antoine Pitrou wrote:
> On Mon, 17 Mar 2014 13:02:23 -0700
> Sean Felipe Wolfe wrote:
>> I'm getting my feet wet with the cpython
On Mon, 17 Mar 2014 13:02:23 -0700
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?
This is a classic hg question, you would g
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 on
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?
I'm expecting different branches to be kept discreetly. If I switch to
3.3, then I expect to see only 3.3 com
