Largefiles broken?

[Matt Harbison]

dukeofgaming <dukeofgaming <at> gmail.com> writes:

... 
> [largefiles]
> patterns = re:.*\.bin|pyd|exe|zip|rar|jpg|png|bmp|a|so|swf|fla|hex|out)$
> 
> minsize = 10
> usercache = D:\hglfcache
>
> When are the previous parameters supposed to kick in?, only in lfconvert? I
> think they should kick in on an add/addremove operation as well., if not,
> what is the point to the pattern/minsize parameters?

If it is a repo that doesn't currently have a largefile in it, you need to
explicitly opt in to use largefiles- enabling the extension isn't enough.  The
last paragraph of 'hg help largefiles' mentions the repo must 'contain' a
largefile, but that's somewhat ambiguous.

Prior to 2.3.2, this meant an 'hg add --large' of at least one file, plus a
commit before the pattern and size options would be used.  With 2.3.2 and
later, you don't need the commit.  So you can pick out a file you want to be
large and add it with --large, and then 'hg addremove' to pick up the rest
based on the size and pattern before the commit.

I also had a patch to add the --large option to init so you don't have to
explicitly add the first file, but there were issues with how to remember this
option was used before files get added, and I haven't been motivated enough to
work on it more.

--Matt