unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Dan Nicolaescu <dann@ics.uci.edu>
To: Miles Bader <miles@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: GIT uppercase annoying
Date: Tue, 31 Jul 2007 18:20:46 -0700	[thread overview]
Message-ID: <200708010120.l711KkLA019354@oogie-boogie.ics.uci.edu> (raw)
In-Reply-To: <87tzrk450f.fsf@catnip.gol.com> (Miles Bader's message of "Wed\, 01 Aug 2007 06\:50\:24 +0900")

Miles Bader <miles@gnu.org> writes:

  > Hi,
  > 
  > The vc-handled-backends entry for git and other new backends are ALL
  > UPPERCASE, which seems rather at odds with the way I've seen their names
  > used generally (I know historical entries like CVS and RCS are
  > uppercase, but they're traditinally _always_ written that way).
  > 
  > It may seem like a minor point, but this name is _constantly_ visible
  > because it's used for the mode-line display of files under version
  > control; while visiting files handled by git, in particular, I've found
  > this quite distracting (whereas I don't notice for files in CVS, becasue
  > I'm so used to uppercase "CVS").  Git doesn't really stand for anything,
  > and is most commonly used like a word, not an acronym; I gather the same
  > is true of systems like Bzr though I have less familiarity with them.
  > 
  > The current "all uppercase" nature of vc-handled-backends seems mostly
  > like people just copied the casification of the older entries when
  > adding new ones, but I'd really like to quash this trend and use a less
  > annoying convention for backends where that is more natural.

FWIW I agree. 
When I checked in vc-hg.el, someone asked for Hg (or hg?) to be
changed to HG...

  reply	other threads:[~2007-08-01  1:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-07-31 21:50 GIT uppercase annoying Miles Bader
2007-08-01  1:20 ` Dan Nicolaescu [this message]
2007-08-01  3:17   ` Miles Bader
2007-08-01  3:45     ` Dan Nicolaescu
2007-08-01  3:57       ` Miles Bader
2007-08-01 14:11       ` Stefan Monnier
2007-08-02  6:09         ` Miles Bader

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://www.gnu.org/software/emacs/

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

  git send-email \
    --in-reply-to=200708010120.l711KkLA019354@oogie-boogie.ics.uci.edu \
    --to=dann@ics.uci.edu \
    --cc=emacs-devel@gnu.org \
    --cc=miles@gnu.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/emacs.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).