Simon Heimberg <simohe@besonet.ch> [Sat, 28 Jul 2012 22:36:22 +0200] rev 17273
peer: delete double definition of method peer
FUJIWARA Katsunori <foozy@lares.dti.ne.jp> [Sat, 28 Jul 2012 23:51:57 +0900] rev 17272
revset: fix the definition of "unstable changesets" for "unstable" predicate
unstable-ness of changesets should be determined by obsolete-ness of
not descendants but ancestors.
Matt Harbison <matt_harbison@yahoo.com> [Fri, 20 Jul 2012 19:08:26 -0400] rev 17271
largefiles: support revsets for outgoing --large
Previous to this, outgoing with a revset succeeded unless --large was also
specified.
Matt Harbison <matt_harbison@yahoo.com> [Fri, 20 Jul 2012 23:50:52 -0400] rev 17270
largefiles: fix a traceback introduced with recent peer changes
Changeset 1ac628cd7113 broke 'outgoing --large'
...
File "hgext\largefiles\lfutil.py", line 56, in findoutgoing
remote.local(), force=force)
File "mercurial\discovery.py", line 31, in findcommonincoming
if not remote.capable('getbundle'):
AttributeError: 'lfilesrepo' object has no attribute 'capable'
This restores the previous functionality, though I'm not sure if there's a
better way to do this- that changeset introduces a hunk in debugdiscovery that
does this:
if not util.safehasattr(remote, 'branches'):
# enable in-client legacy support
remote = localrepo.locallegacypeer(remote.local())
Is there a legacy support issue here too?
Matt Harbison <matt_harbison@yahoo.com> [Fri, 20 Jul 2012 19:14:41 -0400] rev 17269
largefiles: support revsets for cat
Previous to this, cat only accepted revsets if the largefiles extension was
disabled.
Matt Harbison <matt_harbison@yahoo.com> [Fri, 20 Jul 2012 18:13:19 -0400] rev 17268
largefiles: support revsets for revert
Previous to this, revert only accepted revsets if the largefiles extension was
disabled.