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

Na'Tosha Bard natosha at unity3d.com
Fri Aug 5 03:05:10 CDT 2011


On Thu, Aug 4, 2011 at 4:12 PM, Andrew Pritchard <awpritchard at gmail.com>wrote:

> The largefiles rename is done, and the Kiln-specific bits are now split out
> into their own meta-extension.  We have moved it out of the old repository
> into
> a more appropriately-named one at
> https://developers.kilnhg.com/Repo/Kiln/largefiles/largefiles.  At this
> point,
> there shouldn't be any remaining naming or copyright concerns, so the focus
> can
> be placed on anything that would block largefiles' inclusion in Mercurial's
> bundled extensions.
>

OK, so now that the copyright stuff is out of the way, I think we have at
least the following issue left: documentation for users who are not using
Kiln.  The one time we tried setting up the then-called kbfiles here at
Unity without Kiln, we were successful, but only after writing our own FTP
store.  It seems like you've fixed this in largefiles, with a default store
option for people who don't have Kiln, but we need a nice gude for users to
actually set it up.

Also, I've been submitting fixes for bugs upstream by pushing to Unity's
branch for the old kbfiles repository.  Do we need a new branch for the
largefiles repository?  Additionally, can I have people on my team start
testing largefiles with Kiln, or will it break?

I wonder if Matt also has a list of stuff he wants addressed?

Cheers,
Na'Tosha

-- 
*Na'Tosha Bard*
Build & Infrastructure Developer | Unity Technologies

*E-Mail:* natosha at unity3d.com
*Skype:* natosha.bard
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20110805/6c4c6556/attachment.html>


More information about the Mercurial-devel mailing list