[Bug 3541] New: largefiles enabled repo needs an initial commit
bugzilla-daemon at bz.selenic.com
bugzilla-daemon at bz.selenic.com
Fri Jul 13 18:19:14 CDT 2012
http://bz.selenic.com/show_bug.cgi?id=3541
Priority: normal
Bug ID: 3541
CC: mercurial-devel at selenic.com, natosha at gmail.com
Assignee: bugzilla at selenic.com
Summary: largefiles enabled repo needs an initial commit
Severity: bug
Classification: Unclassified
OS: Linux
Reporter: chris_wachter at hotmail.com
Hardware: PC
Status: UNCONFIRMED
Version: 2.2.2
Component: largefiles
Product: Mercurial
It appears that a repo is not made aware of its largefiles-enabled status until
a commit is made.
This can cause some odd behavior - addremove will add a file twice (as an
additional standard file in addition to the largefile version) until that first
commit is made. Also, files above largefile's minimum size threshold are not
added as largefiles until that initial commit.
After that, things work as advertised.
Example (linux/bash):
> mkdir test; cd test
> hg version | head -n 1
Mercurial Distributed SCM (version 2.2.2)
> hg init
> touch foo
> hg add --large foo
> hg stat
A foo
> hg addremove
adding foo
> hg stat
A foo
A foo
> hg ci -vm 'test'
.hglf/foo
foo
calling hook commit.lfiles: <function checkrequireslfiles at 0x53c3668>
committed changeset 0:97ced15c4071
>> touch bar
> hg add --large bar
> hg addremove
> hg ci -vm 'test2'
.hglf/bar
calling hook commit.lfiles: <function checkrequireslfiles at 0x1a9e9668>
committed changeset 1:31885e85a412
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the Mercurial-devel
mailing list