Repository navigation
Conversation
On Windows, UNC paths are a very convenient way to share data, and alternates are all about sharing data. We fixed a bug where alternates specifying UNC paths were not handled properly, and it is high time that we add a regression test to ensure that this bug is not reintroduced. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de>
|
/submit |
|
Submitted as pull.140.git.gitgitgadget@gmail.com |
|
This branch is now known as |
|
This patch series was integrated into pu via git@f0c0adb. |
|
This patch series was integrated into pu via git@ae31419. |
|
This patch series was integrated into pu via git@d616b47. |
|
This patch series was integrated into pu via git@60839fe. |
|
This patch series was integrated into pu via git@380c54e. |
|
This patch series was integrated into pu via git@ddc59e9. |
|
This patch series was integrated into pu via git@34a0e77. |
|
This patch series was integrated into pu via git@6a538c1. |
|
This patch series was integrated into next via git@dfff4a6. |
|
This patch series was integrated into pu via git@0684276. |
|
This patch series was integrated into pu via git@0b076b4. |
|
This patch series was integrated into next via git@0b076b4. |
|
This patch series was integrated into master via git@0b076b4. |
|
Closed via 0b076b4. |
This was fixed in git.git's
mastersome time ago, unfortunately not upstreamed from Git for Windows' patch thicket (my fault, or better put: the fault of the twenty-four hour days not being longer). We carried a regression test on top of the fix, and I can at least contribute that.