[Python-Dev] Status of 3.2 in Hg repository? (original) (raw)
Tim Peters tim.peters at gmail.com
Wed Aug 21 21:37:23 CEST 2013
- Previous message: [Python-Dev] Status of 3.2 in Hg repository?
- Next message: [Python-Dev] PEP 446: issue with sockets
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
[Tim]
BTW, it's not quite a null-merge. The v3.2.5 release tag doesn't currently exist in the 3.3 or default .hgtags files. So long as 3.2 has a topological head, people on the 3.3 and default branches won't notice (unless they look directly at .hgtags - they can still use "v3.2.5" in hg commands successfully), but that's mighty obscure ;-)
[Éric Araujo]
IIRC Mercurial looks at the union of .hgtags in all unmerged heads to produce the list of existing tags. :-)
Right! That's the obscure reason why v3.2.5 works even on branches where .hgtags doesn't contain a v3.2.5 entry - but will fail if 3.2 ceases to have "a topological head" (unless 3.2's .hgtags is merged to a still-active branch).
- Previous message: [Python-Dev] Status of 3.2 in Hg repository?
- Next message: [Python-Dev] PEP 446: issue with sockets
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]