Update of sr #110932 (project administration):
Status: None => Done
Assigned to: None => rwp
Open/Closed: Open => Closed
_______________________________________________________
Follow-up Comment #4:
> Could that be fixed for the `/r/` URLs?
No. Doing so would BREAK raw file access which provides access to the
config file, the hook script files, and the other things one can only
access using the raw file access. That's the entire point of the /r/
raw path. And there is no need for setting up /r/ as a smart protocol
when /git/ is the smart protocol.
Basically if one were going to change /r/ from raw to smart then there
is absoluetely no purpose in /r/ at all. If that were to be done then
removing it entirely would make the most sense because the /git/
implements the smart protocol already. Just use /git/.
The git program is adaptive and will work with different upstream
protocols. It works best with the smart protocol. It works with raw
file access. It will also work with the cgit path too, though I
personally think that would be silly, and also inefficient. Just
because one can do something does not mean one should do something.
Illustrating that I mention RFC1149.
https://www.rfc-editor.org/rfc/rfc1149
It would be useful to know why git:// does not work here. I don't
know why it would not. It's a git smart protocol server.
The best smart protocol is of course member access over ssh. That
connects up the git client with the git server directly. Currently
only supported for member access due to technical reasons but if the
problems were worked through it could be possible to use it for
anonymous read-only access too.
_______________________________________________________
Reply to this item at:
<https://savannah.nongnu.org/support/?110932>
_______________________________________________
Message sent via Savannah
https://savannah.nongnu.org/
