[issue1810] fetch extension complains about uncommited local changes when there are none

Moist mercurial-bugs at selenic.com
Mon Aug 24 09:33:17 CDT 2009


New submission from Moist <afoo42 at gmail.com>:

I'm using Mercurial 1.3.1 on Debian GNU/Linux with Python 2.5.4 on amd64.

Here's a demonstration of the bug:
--snipp--
moist:/tmp% mkdir test; cd test
moist:/tmp/test% hg init
moist:/tmp/test% echo foo > foo
moist:/tmp/test% hg add
adding foo
moist:/tmp/test% hg ci -m foo
foo
committed changeset 0:eb0fb1c95db7
moist:/tmp/test% mkdir ../t; cd ../t
moist:/tmp/t% hg clone /tmp/test
destination directory: test
updating working directory
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
moist:/tmp/t% cd test
foo
moist:/tmp/t/test% echo bar > bar
moist:/tmp/t/test% hg add
adding bar
moist:/tmp/t/test% hg ci -m bar
bar
committed changeset 1:6149ed96da59
moist:/tmp/t/test% cd ../../test
foo
moist:/tmp/test% echo spam > spam
moist:/tmp/test% hg add
adding spam
moist:/tmp/test% hg ci -m spam
spam
committed changeset 1:fa52a4563e47
moist:/tmp/test% cd ../t/test
bar  foo
moist:/tmp/t/test% hg st
moist:/tmp/t/test% hg fetch
pulling from /tmp/test
searching for changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 1 changes to 1 files (+1 heads)
updating to 2:fa52a4563e47
1 files updated, 0 files merged, 1 files removed, 0 files unresolved
merging with 1:6149ed96da59
abort: outstanding uncommitted changes (use 'hg status' to list changes)
moist:255:/tmp/t/test% hg st
moist:/tmp/t/test% hg ci -m what
nothing changed
--snapp--

----------
messages: 10414
nosy: moist
priority: bug
status: unread
title: fetch extension complains about uncommited local changes when there are none

____________________________________________________
Mercurial issue tracker <mercurial-bugs at selenic.com>
<http://mercurial.selenic.com/bts/issue1810>
____________________________________________________



More information about the Mercurial-devel mailing list