[clone to a case-sensitive medium, did not help]

[Uwe Brauer]

>>> "RW" == Rainer Woitok <rainer.woitok at gmail.com> writes:

> Uwe,
> On Friday, 2021-06-04 17:41:55 +0200, you wrote:

>> ...
>> It took me some time to format a USB with HFS+ case sensitve and
>> journaling disabled.
>> 
>> 1. I switched to that medium,
>> 
>> 2. I checked that it is case sensitive.
>> 
>> 3. I cloned the repository.
>> 
>> 4. I run Rainer's recomendations:
>> 
>> ,----
>> | hg mv Mini-Examen-Quim/13-14/Result-Final/CALIFICACIONES_EstadisticaCalcNumerico13-14.csv Mini-Examen-Quim/13-14/Result-Final/steve
>> | hg ci -m "First move"
>> | hg mv Mini-Examen-Quim/13-14/Result-Final/steve Mini-Examen-Quim/13-14/Result-Final/Calificaciones_EstadisticaCalcNumerico13-14.csv 
>> | hg ci -m "Second move"
>> `----

> Strictly speaking,  on a case respecting file system you could have done
> this with a single  "hg mv" command  because files  "*/Calificaciones_*"
> and "*/CALIFICACIONES_*" are different files due to their dirrerent nam-
> es.


Yeah but it didn't

>> 1. From my mac disk I pull the 'repaired' repository.
>> 
>> 2. But hg up english 

> I'm still  not quite sure  what precisely  your problem is.   Is there a
> file  "*/Calificaciones_*"  in branch  "default"  while there  is a file
> "*/CALIFICACIONES_*" in branch "english" (or vice versa)?   In that case
> "hg up -C english"  might help  because it would  remove the conflicting
> file in branch "default" from the working directory  before checking out
> branch "english".


In a nutshell, I *need* to upgrade to the english branch and I can't. I
think this is quite serious.

I don't know what is in the english branch, since I can't visit it, I
don't know.

The default branch now contains only 

Cal_estadcalnum13-14.csv

Since I renamed this file.



 hg up -C english

Does *not* help


So this is why I am so puzzled. I start to have the feeling that there
is a but somewhere.


> But since thanks to Bill Gates -- and as I was supprised to learn lately
> also Steve Jobs  -- the vast majority  of file systems  in this world is
> case agnostic, 

I talked to MaC guy. He claims the true culprit is adobe, they are
relying on such an old scheme (all their pkg are case insensitive) that
users run into problems using their software on a case-sensitive Mac
system.

Well one reason more not to use adobe software other than pdf files.


> I'd say that having different files in different branches
> with names only differing in case  generally is a BAD IDEA (tm).   Can't
> you rather put  ".gb" or ".en"  in the conflicting file names  in branch
> "english"?  Then case would again be irrelevant.

    1. First of all, I am not a huge fan of renaming since it confuses hg
       annotate, which I use quite a bit. The file however is not
       important so I could do that, but

    2. secondly  since I cannot visit the english branch I am stuck, do
       we have a catch 22 here?


I can't wait to reformat the whole f.. Disk.

Uwe 



-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 5673 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20210605/2b57abc6/attachment.p7s>