[RFC] kbfiles: an extension to track binary files with less wasted bandwidth

[Andrew Pritchard]

> Is there a short introduction anywhere from which we can learn how to
> test this?  If not, can you summarise here?

As of about five minutes ago, there's a short introduction at
https://developers.kilnhg.com/Repo/Kiln/largefiles/largefiles/File/usage.txt,
but the gist of it is that all you have to do for new large files and
new repositories is enable the largefiles extension on all clients and
servers, and use 'hg add --large', and old repositories can be
converted with 'hg lfconvert'.

> the help text points at a usage.txt file that doesn't exist
> and gives a canonical URL for it that doesn't resolve;

Just fixed that as well; it now points to the URL I just gave you.

> "help lfconvert" points to the lfput command which also appears not to
> exist;

I hadn't noticed that; I'll look into it now.

> and design.txt (the only apparent documentation outside the
> code) still refers to bfiles throughout.

That's also fixed as of five minutes ago.

> (I've never used bfiles either, for what it's worth -- I don't know
> whether that's likely to be good or bad in learning about this one.)

That's probably a good thing: largefiles aims to be largely (ha!)
transparent to the user, other than 'add --large' to force files to be
tracked as largefiles and requiring network access for updates to new
revisions, whereas bfiles is very hands-on with bfile management,
requiring the user to think of them as an entirely separate kind of
entity from normal tracked files.