Hi Rasmus,
On 2024-06-12 1:18 pm, Rasmus Villemoes wrote:
On 12/06/2024 12.20, Claudius Heine wrote:
Hi everyone,
in the past we used cgit, which provided cloning the u-boot repo via
http, https, ssh and the git protocol.
When we migrated to gitlab, which doesn't support the git protocol, we
implemented some additional service files to continue to support it for
some of our git repositories.
We just noticed that cloning via the git protocol is currently broken,
likely some changes in gitlab happened and we would need to recreate the
symlinks on the server to point to the right repositories again.
Since that is another thing to maintain and keep up, we would like to
just shut the git protocol down. AFAIK most projects moved to use https
for cloning anyway, since there were not many reports of broken cloning.
What are your thoughts? Is it worth the effort to keep the git protocol up?
So I don't think you should necessarily keep the git:// working if it
means extra maintenance. I just checked a couple of my local copies of
u-boot.git (don't ask, it's many different customer projects) and it
seems to be more or less random if I added upstream with git:// or
https:// . I can certainly change those, and thanks for the heads up.
I'm just wondering if it's possible to have the server send some message
to the client when the git protocol is used, for some deprecation period
(6 months?), so a developer doing "git remote update" will get notified.
He would then also have a chance to propagate that to whatever local CI
he's responsible for, instead of only noticing when things do start
breaking.
We are using `git-daemon` and there is a `--accept-hook` which can print
a single line to the requestor, but only if the request is denied.
So there doesn't seem to be a way to implement a deprecation period.
regards,
Claudius
--
DENX Software Engineering GmbH, Managing Director: Erika Unter
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-54 Fax: (+49)-8142-66989-80 Email: c...@denx.de
