From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([2001:4830:134:3::10]:56014) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eqj0w-0006WQ-W5 for guix-patches@gnu.org; Tue, 27 Feb 2018 12:26:07 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eqj0s-0006W3-1h for guix-patches@gnu.org; Tue, 27 Feb 2018 12:26:06 -0500 Received: from debbugs.gnu.org ([208.118.235.43]:56215) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eqj0r-0006Vw-So for guix-patches@gnu.org; Tue, 27 Feb 2018 12:26:01 -0500 Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eqj0r-0001p4-M1 for guix-patches@gnu.org; Tue, 27 Feb 2018 12:26:01 -0500 Subject: [bug#29820] [PATCH] services: cgit: Add more configuration fields. Resent-Message-ID: From: ludo@gnu.org (Ludovic =?UTF-8?Q?Court=C3=A8s?=) References: <87incy9yv6.fsf@gmail.com> <87h8sdb6qa.fsf@lassieur.org> <87po6yu7h9.fsf@gmail.com> <871sjdz8ca.fsf@lassieur.org> <87r2q6zp2l.fsf@gmail.com> <87h8q6at2i.fsf@lassieur.org> <87muzxej3o.fsf@gmail.com> <87efl9beff.fsf@lassieur.org> Date: Tue, 27 Feb 2018 18:25:19 +0100 In-Reply-To: <87efl9beff.fsf@lassieur.org> ("=?UTF-8?Q?Cl=C3=A9ment?= Lassieur"'s message of "Sun, 25 Feb 2018 10:34:44 +0100") Message-ID: <871sh6z6o0.fsf@gnu.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-patches-bounces+kyle=kyleam.com@gnu.org Sender: "Guix-patches" To: =?UTF-8?Q?Cl=C3=A9ment?= Lassieur Cc: 29820@debbugs.gnu.org Cl=C3=A9ment Lassieur skribis: > Oleg Pykhalov writes: > >> OK. Also I see in cgit README [1], they use =E2=80=9Ccgit=E2=80=9D even= in titles. >> >> On the other hand it feels wrong to me, because it's a name of the >> program, like Guile, Guix, Linux or Emacs. It might be better to stick >> to that convention for readability (e.g. not =E2=80=98cgit=E2=80=99 as a= command or a >> file name, but as a project name =E2=80=9CCgit=E2=80=9D). And because o= f we rename even >> configuration options like =E2=80=98scan-path=E2=80=99, it's OK to force= the >> capitalization also. WDYT? > > Our convention is to follow upstream convention. Guile, Linux, Emacs > are all capitalized upsteam, which is why they are capitalized in Guix > documentation. It's up to the upstream project to choose. > > Plus, cgit seems to pay a lot of attention to it. See, the title is: > cgit - CGI for Git > And then: > Building cgit involves building a proper version of Git. > > Clearly they acknowledge that Git is capitalized (because upstream > decided so), but cgit is not. > > So I think we should not capitalize it :-) Agreed. (Though again we should not lose our hair over it. :-)) Ludo=E2=80=99.