Tony Hansen
Results
27
comments of
Tony Hansen
In addition, github.com appears to no longer support the git:// protocol: https://github.blog/2021-09-01-improving-git-protocol-security-github/ > No more unauthenticated Git > > On the Git protocol side, unencrypted git:// offers no integrity or...
wouldn't URI.parse allow you to grab the path separately from the fqdn?
I say: accept the risk and go with case-sensitive then case-insensitive.
I've seen too many files copied piecemeal from one project to another. IMHO, **_NOT_** having the info there is **_asking for trouble_**. I'd even go so far as to suggest...
If wave bonding was enabled for the print, it will have 6 '_processed's at the end of the name.
I ran into the same problem.