Windows people: please help check idea for a new Mercurial repository layout

[Adrian Buehlmann]

On 16.06.2008 13:58, Peter Arrenbrecht wrote:
> This may be a rather unconventional idea, but I'll air it
> nevertheless. Maybe it's going to trigger other ideas and eventually
> lead somewhere.
> 
> How about simply skipping aux.i/.d et al. when encountering them on
> Windows? This would make all accesses to the index/data of such files
> fail. As I see it, this would have the following consequences:
> 
> a) You cannot clone such a repo over the wire. Good.

No. that's bad and entierly unneeded.

If I have a repo on a unix box that is intended to be used on
Windows *and* unix in a mixed platform project and someone
stupidly checks in a file or dir with the name aux (on unix, obviously),
then realizes his error (maybe after a friendly Windows colleague telling him),
checks in another change that deletes the offending
file again, I can't clone that repo to windows never ever again,
although I don't even want to checkout that borked changeset.

> b) You can clone such a repo locally when the clone operation is just
> linking/copying .hg/store based on a walk of .hg/store. Good.
> c) You cannot update to a revision in which aux is alive. Acceptable
> (see below)?
> d) You can update to a revision in which aux is no longer present
> (renamed, dropped). Good.
> e) You can push csets from this repo as long as aux is not involved. Good.
> f) You can pull from such a repo csets where aux is not involved. Good.
> g) Verify would fail. Good.

Hell no.

> h) The repo does not constitute a complete backup of the original
> repo. Acceptable?

Absolutely not.