"unsynced changes" error on push

[Christian Ebert]

* Martin Geisler on Friday, May 06, 2011 at 16:49:40 +0200
> Christian Ebert <blacktrash at gmx.net> writes:
>> * Antoine Pitrou on Friday, May 06, 2011 at 13:31:56 +0000
>>> What does the "unsynced changes" error on push mean? See below:
>>> 
>>> $ LANG=C hg in
>>> comparing with ssh://hg@hg.python.org/cpython/
>>> searching for changes
>>> no changes found
>>> 
>>> $ LANG=C hg push -v --debug
>>> pushing to ssh://hg@hg.python.org/cpython/
>>> abort: push failed:
>>> 'unsynced changes'
>>> 
>>> $ hg version
>>> Mercurial Distributed SCM (version 1.8.3+58-3a90fb3addc1)
>> 
>> I had this as well for a short time. If I'm not mistaken it was
>> fixed in:
>> 
>> changeset:   14199:e3dd3dcd6059
>> user:        Peter Arrenbrecht <peter.arrenbrecht at gmail.com>
>> date:        Thu May 05 12:53:33 2011 +0200
>> files:       mercurial/treediscovery.py tests/test-treediscovery.t
>> description:
>> treediscovery: fix regression when run against older repos (issue2793)
>> 
>> See also:
>> http://mercurial.selenic.com/bts/issue2793
> 
> That is correct. A 'hg push --force' will also work for the affected
> versions.

Not to bitbucket over ssh though.
-- 
So dacht ich. Nächstens mehr.
_HÖLDERLIN:  HYPERION_  --->> http://www.blacktrash.org/hyperion