> On 2021-06-04 08:41, Uwe Brauer wrote: > If what you're concerned about is the data in the files, can't > you just use a case-sensitive filesystem to rename one > case-version to a completely different name and just leave it > like that? That is, just do something like your first hg mv > above, renaming the file to something completely different, > and then pull that, without renaming it back to the > case-colliding name? Is it important that the file have that > particular name?
No it is not, so on the case-insensitive filestyem I tried hg mv Calificaciones_EstadisticaCalcNumerico13-14.csv Cal_estadcalnum13-14.csv hg ci -m "Rename case collision file" So tip does not contain the file that causes the collision, *but* hg up english gave me abort: case-folding collision between Mini-Examen-Quim/13-14/Result-Final/Calificaciones_EstadisticaCalcNumerico13-14.csv and Mini-Examen-Quim/13-14/Result-Final/CALIFICACIONES_EstadisticaCalcNumerico13-14.csv Which confuses me because Calificaciones_EstadisticaCalcNumerico13-14.csv is no longer in tip. > Also, if I read your error right, you are getting a collision > involve a file that no longer exists (the uppercase version, > which is gone since you renamed it to a different case). Are > you sure you're making the changes in right branch and/or > updating to the right revision? Yes, quite confident.
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Mercurial mailing list [email protected] https://www.mercurial-scm.org/mailman/listinfo/mercurial
