all messages for Guix-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleg Pykhalov <go.wigust@gmail.com>
To: "Clément Lassieur" <clement@lassieur.org>
Cc: 29820@debbugs.gnu.org
Subject: [bug#29820] [PATCH] services: cgit: Add more configuration fields.
Date: Sun, 25 Feb 2018 08:25:31 +0300	[thread overview]
Message-ID: <87muzxej3o.fsf@gmail.com> (raw)
In-Reply-To: <87h8q6at2i.fsf@lassieur.org> ("Clément Lassieur"'s message of "Sun, 25 Feb 2018 00:03:49 +0100")

[-- Attachment #1: Type: text/plain, Size: 1274 bytes --]

Hello Clément,

Clément Lassieur <clement@lassieur.org> writes:

[...]

>>>>> I think the official project uses 'cgit' instead of 'Cgit' (there are
>>>>> other occurrences where you use 'Cgit').
>>>>
>>>> Ludovic asked to capitalize cgit in
>>>> https://debbugs.gnu.org/cgi/bugreport.cgi?bug=28283#14
>>>
>>> But he was only talking about titles wasn't he?
>>
>> I think not only, because we have Cgit everywhere in the current
>> documentation.
>
> Then it should be changed to 'cgit', there is no need to copy
> documentation mistakes :-).  This is an example of commit from Ludovic
> where he doesn't capitalize 'zlib':
> https://git.savannah.gnu.org/cgit/guix.git/commit/?id=06e3a5181efa0ea83bb6608d3cbfba5caa56d7e9.

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?

[1] https://git.zx2c4.com/cgit/tree/README

Thanks,
Oleg.

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 832 bytes --]

  parent reply	other threads:[~2018-02-25  5: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 [this message]
2018-02-25  9:34             ` Clément Lassieur
2018-02-27 17:25               ` Ludovic Courtès
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87muzxej3o.fsf@gmail.com \
    --to=go.wigust@gmail.com \
    --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 external index

	https://git.savannah.gnu.org/cgit/guix.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.