![]() Where a resolver type traits exists given the previous resolved type: * Here fold will not use std::pair, but a resolver type that takes both A and B and gives back the resolved B */Ĭlass is actually not restricted to any class type it might hold. Let me illustrate this with a quick example: The leftmost type never contains placeholders. The placeholders "real" type can only be known when both having the fully expanded type to the left as well as the unexpanded type. The reason why I need this, is because the types which have to be "folded" can be placeholder types. Std::pair, long> /* the previous type again */ This also dives rather deep into Mercurial internals though, so you should avoid it unless as a last resort. This is NOT recommended for non expert Mercurial users.Īnother similar manual method is described here: ![]() Revision for example, please see the Wiki page below:: Revision causing case-folding collision on case-insensitiveįilesystems, to rename colliding files or browsing contents at such If you want to (or need to) update working directory by the With recent Mercurial, you can change case of filename safely in stepsīelow, even on case-insensitive filesystems:: In this case, files in one of them or both should be renamed to avoid Revisions successes, collision occurs between revision to be merged. ![]() Revisions on case-insensitive filesystems, please see 'Updating If you want to (or need to) browse or repair such The colliding files on a case-sensitive filesystem, and commit them to ![]() To repair such revisions, you should give new names to one or both of On case-insensitive filesystems, updating to revisions which haveįiles with case collisions will abort, even with Help topic being worked on that will be included in the next version of Mercurial: ![]()
0 Comments
Leave a Reply. |