Question about case-folding issue

[Josh Malinski]

I ran into an issue with case-folding, which I have since fixed, I was
looking at some of the extensions which prevent such issues from
happening. The caseguard and fixcase extensions are interesting to me,
however I had a procedural question that seems very newbie but I don't
know exactly how it will work.

 

What is the expected result when using the caseguard or fixcase
extension with the following process;

 

Add foo.a

Commit rev 1

Add foo.b

Commit rev 2

Update rev 1

Add foo.B w/ new branch

Commit rev 3

Merge rev 3 and 2

Commit rev 4

Add foo.c

Commit rev 5

 

At this point if I try to clone or update I will get a case-fold issue
because foo.b and foo.B are the same in windows but not in the repo. I
understand what the problem is but how would caseguard and fixcase
prevent them from happening if I updated to rev 1 where foo.b hadn't
been added yet? Or is it because I already committed and it is being
tracked it won't allow it to happen because of it.

 

I am a little confused, and any clarification would be great.

 

 

--Josh

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial/attachments/20100406/aeda1f61/attachment.htm>