git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <junkio@cox.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Pavel Roskin <proski@gnu.org>, git@vger.kernel.org
Subject: Re: Sanity check of git-commit patch, was Re: [PATCH] Making CFLAGS compilant with GNU Coding Standards
Date: Tue, 09 Aug 2005 10:00:39 -0700	[thread overview]
Message-ID: <7vd5onvydk.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <Pine.LNX.4.63.0508091618320.7995@wgmdd8.biozentrum.uni-wuerzburg.de> (Johannes Schindelin's message of "Tue, 9 Aug 2005 16:19:13 +0200 (CEST)")

Johannes Schindelin <Johannes.Schindelin@gmx.de> writes:

>> True.  My bad old habit.
>
> An elegant method to do that:
>
> case --some-long-option in "$1"*) ..; esac

You are almost correct, but you need to realize that I generate
that long "case -s|--s|--so|--som|..." chain using a script that
takes all potential option names as its arguments, and makes
case arms that contain only unambiguous ones, so that I can
handle --some-long-option and --some-other-long-option sensibly.

Also you forgot to grok --some-option-with-args=* in your
version ;-).

  reply	other threads:[~2005-08-09 17:00 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-08-06  5:36 [PATCH] Making CFLAGS compilant with GNU Coding Standards Pavel Roskin
2005-08-08 20:53 ` Junio C Hamano
2005-08-08 23:10   ` Ryan Anderson
2005-08-08 23:42     ` Johannes Schindelin
2005-08-09  2:48       ` Junio C Hamano
2005-08-09 10:17         ` Sanity check of git-commit patch, was " Johannes Schindelin
2005-08-09 12:53           ` Junio C Hamano
2005-08-09 14:19             ` Johannes Schindelin
2005-08-09 17:00               ` Junio C Hamano [this message]
2005-08-10  2:20                 ` Horst von Brand
2005-08-10 12:52                   ` Johannes Schindelin
2005-08-10  5:45             ` Junio C Hamano
2005-08-09 12:56     ` Junio C Hamano
2005-08-11  4:01   ` Pavel Roskin

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=7vd5onvydk.fsf@assigned-by-dhcp.cox.net \
    --to=junkio@cox.net \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=proski@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. 
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).