«large» files.

[Uwe Brauer]

>>> "Matt" == Matt Harbison <mharbison72 at gmail.com> writes:

    >> On Apr 22, 2016, at 3:42 AM, Uwe Brauer <oub at mat.ucm.es> wrote:
    >> 
    >> 
>>> On Wed, 20 Apr 2016 09:03:42 -0400, Uwe Brauer <oub at mat.ucm.es> wrote:
    >>> 
    >>> Be aware that you didn't add this as a largefile if you see this
    >>> warning. You need to add a file with --large before any name or size
    >>> based settings you may have setup will be honored.
    >> 
    >> Thanks, this was very helpful. I was not aware that I need to add the
    >> --large option. Now is there a hg command which allows me to find
    >> added large files? Then I could remove and add them but this time with
    >> the appropriate --large option.

    > Remove and add may not be what you want, since there will be a revlog
    > for the file in the history.

Sorry my ignorance, what is the problem with the revlog? Also I must say
that removing and adding is not enough that gets cumbersome then.

    > You may want to rebuild the repo, at least starting from the point
    > where you added the largefile. 

Suppose I decide (which was my case) to put an existing directory of
some dozen (or hundered) files under hg. So I should then check first
the size of all files. Add only those which are smaller than say 10m.
And the rest with the --large option.

What would happen if I added all files with the --large option.


Ok I understand what mercurial is thought to first initialize a repo and
then step by step create and add files, but it is not made (primarily) to
add a directory which already contains a lot files.

Is this correct?

    > There's also 'convert' with a largefile option, but that isn't as
    > feature rich as other conversions. E.g. It may not update .hgtags,
    > and it definitely doesn't update hashes in commit messages. (This
    > is from memory, I don't have the code or hg handy ATM.)

    > Try 'hg files "set:size(>13m)"'. Some versions required the arg to
    > size to be quoted IIRC. This also only works on one revision at a
    > time- it won't see something you added and then moved or removed in
    > the past. You can pass a -r <rev> to look at each revision to find any
    > such files.

Ok my version 3.0.1 does not contain that command. Maybe after all I
should upgrade (and abandon to use tortoisehg).


thanks

Uwe Brauer