Re: «large» files.

[Matt Harbison]

> On Apr 22, 2016, at 5:50 AM, Martijn Pieters <mj at zopatista.com> wrote:
> 
> On 22 April 2016 at 01:35, Matt Harbison <mharbison72 at gmail.com> wrote:
>>> largefile.pdf: up to 51 MB of RAM may be required to manage this file
>>> (use 'hg revert largefile.pdf' to cancel the pending addition)
>> 
>> 
>> 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.
> 
> Perhaps the largefiles extension should augment that warning message
> to point to the `--large` switch if it is loaded?

It obviously would have helped in this case.  OTOH, the reason it ignores the configure parameters until a --large is used is to force people to think about what they are doing to that repo.  I know mpm has pointed out before that people tend to just do what hints say without thinking to make it work, so I'm not sure how this would be received.

> largefile.pdf: up to 51 MB of RAM may be required to manage this file
> (use 'hg revert largefile.pdf' to cancel the pending addition, or use
> hg add --large largefile.pdf to track this as a large file instead)

I forget what 'hg add foo && hg add --large foo' does.  It used to add it both ways, but that's been fixed for a few years now IIRC.  Not sure if that should make it (only) a largefile and keep the message short, or if they should cancel the normal add first.

> -- 
> Martijn Pieters