On 10/10/2019 14:55, Magnus Therning wrote:
Philip Oakley <philipoakley@iee.email> writes:

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...?
Well, I just seem to remember that just a simple case of naming a branch
`my/branch/foo` caused problems when I was using msys/mingw (msys2?) a
few years ago.

I've since not had to work on Windows, so I can't check for myself very
easily.

It's so much better now. It's never been a problem for me in terms of your example of regular branch names.

Mind you I've always bee using the separate bash window using the 'mintty' terminal which comes with G-f-W.

Do pop over to Git-for-Windows some time.

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/4d10b8fa-fc90-517b-4e29-3367520073d8%40iee.email.

Reply via email to