[Python-Dev] forward-porting from 3.1 to 3.2 to 3.3
Éric Araujo
merwok at netwok.org
Sun Mar 13 00:11:34 CET 2011
More information about the Python-Dev mailing list
Sun Mar 13 00:11:34 CET 2011
- Previous message: [Python-Dev] forward-porting from 3.1 to 3.2 to 3.3
- Next message: [Python-Dev] VM and Language summit info for those not at Pycon (and those that are!)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
>> You can’t combine the -r option with other options. (Yes, it’s a known
>> bug.)
> Are you sure? It just worked here: [...]
> (perhaps you're thinking of -R instead?)
Exactly.
>> On an unrelated note, you can use “-r .” to tell Mercurial to find the
>> branch name from the working directory instead of having to remember and
>> retype it.
> Does it work with merges?
It does. hg help revs:
The reserved name "." indicates the working directory parent. If no
working directory is checked out, it is equivalent to null. If an
uncommitted merge is in progress, "." is the revision of the first
parent.
Gotta love consistency, DTRT, Just Working and all that :)
Regards
- Previous message: [Python-Dev] forward-porting from 3.1 to 3.2 to 3.3
- Next message: [Python-Dev] VM and Language summit info for those not at Pycon (and those that are!)
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
More information about the Python-Dev mailing list