On 09/10/2019 08:53, Magnus Therning wrote:
I have a vague memory of there being problems using '/' in branch
names on Windows. Is that still the case?
/M
I don't believe so for 'normal' situations (here I'm thinking of it as a
directory separator or path component separator).
There will still be occasional special cases where the different
"Operating systems" and interface layers (MSYS2, bash) get confused by
the conversions.
However if you have a scenario where on a "Linux" system some one has
been perverse and called a branch "HaHaMS:://??" or similar
"HaHaMS::\\??", and included that in the repository as a public branch
you are expected to open, then yes, you almost certainly will hit the MS
Windows forbidden character/filename issues (other problems include the
AUX and similar special filenames). There can also pathname conversion
issues where the interface layer makes the wrong 'guess'.
This becomes a social problem. It's the same as creating a windows
worktree that has a file called README and a directory called README
side by side, which is a Linux(*nix) D/F conflict failure which Git will
throw out (Linux eating the world, maybe ;-).
Was there a specific instance or type of problem you were thinking of,
in case my ramblings are misplaced...?
Philip
--
You received this message because you are subscribed to the Google Groups "Git for
human beings" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to git-users+unsubscr...@googlegroups.com.
To view this discussion on the web visit
https://groups.google.com/d/msgid/git-users/90bcfdf0-c7f7-7a80-433c-b74df6e4be41%40iee.email.
