Update fails with long file name

[Benjamin Fritz]

On Tue, Sep 29, 2015 at 1:43 AM, Adrian Buehlmann <adrian at cadifra.com>
wrote:
>
> > Seeing as Subversion can handle this file just fine, your explanation
> > may be completely correct but is also condescending, pedantic, and
> > impractical. Mercurial *could* support such files. It chooses not to.
> > And because hg update does not allow ignoring errors of any kind, this
> > makes the entire repository unusable.
>
> It's not impractical. It would be impractical being blamed for creating
> files, which even Windows Explorer can't delete any more.

OK, so that argument was convincing...until I actually tested it.

Using Windows File Explorer in Windows 7, I can delete the file from my SVN
working copy without any problems. I can even send it to the Recycle Bin
and restore it from there. It isn't completely seamless...I can't
copy-paste, I can't rename it to a longer name, and command-line tools
don't work, but I can delete it.

Yes I know the problem is Microsoft's "fault". However, they have provided
a workaround. It's a workaround other applications already use
successfully. And regardless of whose fault it is...Mercurial is the tool
having problems.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20150929/3100d5c2/attachment-0002.html>