Completely baffled

Haszlakiewicz, Eric EHASZLA at transunion.com
Mon Dec 5 11:59:57 CST 2011


> -----Original Message-----
> From: mercurial-bounces at selenic.com [mailto:mercurial-
> 
> 2011/12/5 Liam Routt <liam.routt at mediasaints.com>
> 
> > 	Just as a followup, we managed to lose the last two days of work
> > by one of our developers today with Mercurial, which really hurts.
> 
> My team uses Largefiles heavily and we have not seen this.  Are you

I think I was able to reproduce this, here's a minimal set of commands that causes the modified large file to no longer be modified:

# using bash on Windows XP with Mercurial 2.0 (TortoiseHG)

mkdir x
cd x
hg init foo
hg clone foo bar
cd bar
echo "[extensions]" >> .hg/hgrc
echo "largefiles=" >> .hg/hgrc
cd ../foo
echo "[extensions]" >> .hg/hgrc
echo "largefiles=" >> .hg/hgrc

cd ../bar
dd if=/dev/urandom of=thisfileislarge count=2000

hg add --large thisfileislarge
hg commit -m "add thisfileislarge, which is large, as a largefile"
hg push

echo BLUE | dd bs=1 count=4 conv=notrunc of=thisfileislarge
hg stat

cd ../foo
hg up
echo "blue" > blue
hg add blue
hg ci -m blue

cd ../bar
hg stat

hg pull -u
hg stat


The output I get for that hg pull is:
pulling from C:\Documents and Settings\ehaszla\x\foo
searching for changes
adding changesets
adding manifests
adding file changes
added 1 changesets with 1 changes to 1 files
1 files updated, 0 files merged, 0 files removed, 0 files unresolved
getting changed largefiles
1 largefiles updated, 0 removed

and that final hg stat produces no output.

eric


More information about the Mercurial mailing list