parent -1

[Pierre-Yves David]

On 12/02/2016 09:22 PM, Uwe Brauer wrote:
>
>    > On 11/29/2016 11:29 PM, Uwe Brauer wrote:
>
>    > The warning here means that for some reason some Mercurial internal
>    > state got "corrupt" and was recording a current "checked out" revision
>    > now unknown to Mercurial.
>
> This is most likely the reason for this behaviour the local repo has
> been copied via rsync to a USB stick and then to another machine. Rsync
> is not foolproof (at least I had several data loss issues with it).
>
>
>    >  For some reason, this is not a fatal error
>    > when reading the repository (since operation not touching the working
>    > copy works fine), however this is apparently still just a warning for
>    > operation like commit. In that case, the working copy parent fallback
>    > to nullid.
>
>    > It seems like we should turn the warning into a hard failure in the
>    > case of a commit (or similar operation), can you fill a bug about this
>    > on http://bz.mercurial-scm.org/.
>
> I am not sure what you are suggesting. Do you mean that in the case of
> data corruption, mercurial should *refuse* the commit?
>
> That looks reasonable to me, but I want to be sure.

Yes, in that case, the "warning" should be an abort.

Cheers,

-- 
Pierre-Yves David