1.0 approaches

dhruva dhruvakm at gmail.com
Fri Feb 8 04:20:25 CST 2008


Hi,

On Feb 8, 2008 3:29 PM, Adrian Buehlmann <adrian at cadifra.com> wrote:
>
> http://www.selenic.com/mercurial/bts/issue910 (hg rename -A on Windows deletes
> file if only case changed)
>
> which deletes an uncommitted file.
>
> Also improvements at:
>
> http://www.selenic.com/mercurial/bts/issue912 (hg update fails on Windows if
> case of file changed in repo)
>
> and related:
>
> http://www.selenic.com/mercurial/bts/issue750 (Revisions with case-only renames
> cannot be checkout on case-folding systems)

Is it possible to have something configurable to make toggle case
sensitive/insensitive based on OS? Gradually, all features that get
affected by the case sensitiveness (or lack of it) can be hacked to
get desired behavior.

- One approach could be to have small filters which can normalize
based on settings. The rest of the code can work unmodified
- Second approach would be to have this as a configuration parameter
and use it in every place where it makes a difference.

A filter based approach can be used for a variety of things like:
- End of line treatment
- File name case handling
- Encoding/Decoding or compression/decompression

This will be similar to the Samba VFS layer. You can have a set of
filters through which the data is sent. Each will transform it just a
little bit.

disclaimer: I know very little PYTHON to be able implement this myself!

-dky


-- 
Contents reflect my personal views only!


More information about the Mercurial mailing list