[Mesa-dev] Gitlab migration

Daniel Stone daniel at fooishbar.org
Tue May 29 11:59:11 UTC 2018


On 26 May 2018 at 07:42, Marek Olšák <maraeo at gmail.com> wrote:
> On Thu, May 24, 2018 at 6:46 AM, Daniel Stone <daniel at fooishbar.org> wrote:
>> cgit and anongit will not be orphaned: they remain as push mirrors so
>> are updated simultaneously with GItLab pushes, as will the GitHub
>> mirrors. Realistically, we can't deprecate anongit for a (very) long
>> time due to the millions of Yocto forks which have that URL embedded
>> in their build recipes. Running cgit alongside that is fairly
>> low-intervention. And hey, if we look at the logs in five years' time
>> and see 90% of people still using cgit to browse and not GitLab,
>> that's a pretty strong hint that we should put effort into keeping it.
> Well, I don't know what people are talking about.
> [...]

Probably because it's about subjective opinion rather than objective fact? :)

> OK, that was harsh, but there is a lot of truth to it. I guess GitLab is
> great for admins and I get that. Speaking of the web UI, at least the
> read-only view is impressively unimpressive.

Personally, I much prefer it. My browser content window is around
3200x1700, so I have no problem fitting information in, but I do have
to smash the zoom level up whenever I look at a cgit log; GitLab's
view is about the right density for both my laptop and my phone.
Seeing avatars also helps me skim by quicker visual recognition. If I
ever need to do particularly intense reading or searching which would
take any length of time, I've always just pulled the branch and used
my regular local git tools to examine the repository.

YMMV, and that's fine. But each to their own.


More information about the mesa-dev mailing list