NotificationsYou must be signed in to change notification settings
Fork2.5k
Star10k

alternates: allow relative paths in all repositories#7019

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

ethomson merged 1 commit intolibgit2:mainfromvapier:main

Jan 21, 2025

Merged

alternates: allow relative paths in all repositories#7019

ethomson merged 1 commit intolibgit2:mainfromvapier:main

Jan 21, 2025

Conversation

Copy link

Contributor

The code has behaved this way since it was originally merged in85e7efa1630855c5c8bd9893f732494bda51b591 in PR#719. I can't see an explanation as to why the code decided to only load relative links for the current repo in either place. Maybe git itself used to behave this way, but current versions definitely do not.

FWIW we hit this in CrOS with details inhttps://issuetracker.google.com/214563046, although it's not terribly interesting tbh.