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

Adrian Buehlmann adrian at cadifra.com
Tue Jul 26 14:10:26 CDT 2011


On 2011-07-26 20:23, Andrew Pritchard wrote:
> We are still in the process of cleaning up the code to ship with Mercurial, but
> the current status can be seen at
> http://developers.kilnhg.com/Repo/Kiln/Group/Unstable/Files.  Before the 'real'
> pull request, we will collapse it into a single patch in the hgext directory.
> Planned changes before then include removing compatibility shims for old
> versions of Mercurial and some minor rebranding to remove mentions of 'Kiln'
> from the code and repository layout.
> 
> We would prefer to avoid renaming the extension if possible, both to avoid
> adding extra code to handle both old repositories and new ones and to reflect
> the heritage of the extension, but we understand that parts of the Mercurial
> community may be opposed to the name 'kbfiles', and as such we are willing to
> rename to 'terafiles' if the name would otherwise block the extension from
> shipping with Mercurial.

We got a request to support kbfiles in the TortoiseHg shell extension
(for Windows). I was a bit worried about seeing file paths like
".hg/kilnbfiles/dirstate" (see function openbfdirstate in
kbfiles/bfutil.py).

People may call me paranoid, but the reason why I'm a bit worried is
that the name "Kiln" is a registered trademark by FogCreek [1]. I do not
expect that they would ever forbid anyone using this name, but in theory
they could.

Frankly, I'd prefer not giving any company whatsoever the ability to
"pull the plug" on anything related to Mercurial.

[1] Registration number 3869331, United States Patent and Trademark
Office (see uspto.gov)


More information about the Mercurial-devel mailing list