git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Linus Torvalds <torvalds@osdl.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] Allow '-' in config variable names
Date: Mon, 30 Oct 2006 19:23:20 -0800 (PST)	[thread overview]
Message-ID: <Pine.LNX.4.64.0610301922020.25218@g5.osdl.org> (raw)
In-Reply-To: <7vfyd5rxvg.fsf@assigned-by-dhcp.cox.net>



On Mon, 30 Oct 2006, Junio C Hamano wrote:
> 
> One thing I forgot to add.  Just like we downcase what user has
> written in config file, it might make sense to also remove '-'
> (and if we add '_' to keychar set, that one as well) to when
> canonicalizing the key value.  That way, somewhat awkward long
> configuration variables we currently have can be written more
> readably, e.g. repack.use-delta-base-offset

Well, then we need to teach "git <alias>" that "git <al-i-as>" is the same 
thing as "alias".

> > By the way, everybody seems to do "alias.xxx = -p cat-file -p"
> > (I have it as "git less").  Maybe we would want to make a
> > built-in alias for that?
> 
> Seconds?

I like it mainly as a great example of how to use aliases, not because I 
actually much -use- the thing, so I don't personally care.


  parent reply	other threads:[~2006-10-31  3:23 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-10-30 16:25 [PATCH 1/2] Allow '-' in config variable names Linus Torvalds
2006-10-30 16:28 ` [PATCH 2/2] git push: add verbose flag and allow overriding of default target repository Linus Torvalds
2006-10-30 23:02   ` Junio C Hamano
2006-10-31  3:09   ` Junio C Hamano
2006-10-30 22:45 ` [PATCH 1/2] Allow '-' in config variable names Junio C Hamano
2006-10-31  3:02   ` Junio C Hamano
2006-10-31  3:05     ` J. Bruce Fields
2006-10-31  3:23     ` Linus Torvalds [this message]
2006-10-31  9:49     ` Johannes Schindelin

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=Pine.LNX.4.64.0610301922020.25218@g5.osdl.org \
    --to=torvalds@osdl.org \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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.
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 NNTP newsgroup(s).