From: ludo@gnu.org (Ludovic Courtès)
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 29820@debbugs.gnu.org
Subject: [bug#29820] [PATCH] services: cgit: Add more configuration fields.
Date: Tue, 27 Feb 2018 18:25:19 +0100 [thread overview]
Message-ID: <871sh6z6o0.fsf@gnu.org> (raw)
In-Reply-To: <87efl9beff.fsf@lassieur.org> ("Clément Lassieur"'s message of "Sun, 25 Feb 2018 10:34:44 +0100")
Clément Lassieur <clement@lassieur.org> skribis:
> Oleg Pykhalov <go.wigust@gmail.com> writes:
>
>> OK. Also I see in cgit README [1], they use “cgit” 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 ‘cgit’ as a command or a
>> file name, but as a project name “Cgit”). And because of we rename even
>> configuration options like ‘scan-path’, 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’.
next prev parent reply other threads:[~2018-02-27 17:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-22 22:33 [bug#29820] [PATCH] services: cgit: Add more configuration fields Oleg Pykhalov
2017-12-25 17:00 ` Clément Lassieur
2017-12-26 13:54 ` Clément Lassieur
2017-12-26 19:59 ` Clément Lassieur
2017-12-28 16:45 ` Oleg Pykhalov
2017-12-29 18:40 ` Clément Lassieur
2018-01-31 3:26 ` Oleg Pykhalov
2018-02-24 23:03 ` Clément Lassieur
2018-02-24 23:09 ` Clément Lassieur
2018-02-25 5:25 ` Oleg Pykhalov
2018-02-25 9:34 ` Clément Lassieur
2018-02-27 17:25 ` Ludovic Courtès [this message]
2018-02-28 1:50 ` bug#29820: " Oleg Pykhalov
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871sh6z6o0.fsf@gnu.org \
--to=ludo@gnu.org \
--cc=29820@debbugs.gnu.org \
--cc=clement@lassieur.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).