[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH] Update savannah URLs of gnulib.git files
From: |
Bruno Haible |
Subject: |
Re: [PATCH] Update savannah URLs of gnulib.git files |
Date: |
Sat, 21 Nov 2020 15:18:15 +0100 |
User-agent: |
KMail/5.1.3 (Linux/4.4.0-193-generic; KDE/5.18.0; x86_64; ; ) |
Hi Dmitry,
> * MODULES.html.sh: Prefer cgit URLs over gitweb.
I don't think this is a good idea.
For a particular file, the result of both wget commands is the same.
But the use in such scripts also encourages users to use similar URLs to
access to git repository. Here, gitweb is more human-friendly than cgit.
1) Compare
https://git.savannah.gnu.org/cgit/gnulib.git/
with
https://git.savannah.gnu.org/gitweb/?p=gnulib.git
cgit presents two sections that are practically irrelevant first
(branches that are all more than 2 years old, and tags that are more
than 7 years old).
gitweb presents the recent history of 'master' first. This is what is
most interesting to most people.
2) When displaying diffs: Compare
https://git.savannah.gnu.org/cgit/gnulib.git/commit/?id=7d7d3c0a68e7ed05aef133b8bb9a770a7562891a
with
https://git.savannah.gnu.org/gitweb/?p=gnulib.git;a=commitdiff;h=7d7d3c0a68e7ed05aef133b8bb9a770a7562891a
By default, gitweb highlights changed sections inside a line, which is
often helpful. Whereas cgit, in the default mode, does not do so; this
is less helpful.
In the long run, it pays off to recommend the more human-friendly tool.
Bruno