Completely baffled

[Matt Mackall]

On Tue, 2011-12-06 at 11:10 +1100, Liam Routt wrote:
> Can I say how pleased I was to find this morning (my time) that others 
> had chased this down for me, and that the issue is being progressed. 
> Thanks to all involved.
> 
> I'm new to Mercurial (having fled another DVCS which had a game-breaking 
> flaw in it), so I'm somewhat distressed that what seems to be a fairly 
> straightforward use case somehow seems to have slipped through the 
> cracks. Not being able to do an update without losing local changes to 
> largefiles (assuming that I understand the simple test case) would seem 
> to be a huge failing of basic functionality that should have been caught 
> before the feature was released to the public, I would have thought.

First note that the largefiles code (released Nov 1) is mere months old
and is definitely not up to the level of quality of the rest of
Mercurial yet. It's recently gone from testing by dozens of developers
to hundreds or thousands of end users. Second, it's an extension, which
is our way of saying "this feature is NOT for everyone". If you're
diving into Mercurial with brand-new extensions on day one, you really
can't expect everything to work smoothly.

On the other hand, largefiles definitely is useful to a large class of
experienced users today, which is why it's in the release.

-- 
Mathematics is the supreme nostalgia of our time.