From: Junio C Hamano <gitster@pobox•com>
To: Johannes Schindelin <Johannes.Schindelin@gmx•de>
Cc: Jeff King <peff@peff•net>, Carl Worth <cworth@cworth•org>,
Johannes Sixt <j.sixt@viscovery•net>,
Keith Packard <keithp@keithp•com>,
Git Mailing List <git@vger•kernel.org>
Subject: Re: [PATCH] Add test case for ls-files --with-head
Date: Wed, 03 Oct 2007 14:47:01 -0700 [thread overview]
Message-ID: <7vodffdg6i.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <Pine.LNX.4.64.0710032238080.28395@racer.site> (Johannes Schindelin's message of "Wed, 3 Oct 2007 22:39:48 +0100 (BST)")
Johannes Schindelin <Johannes.Schindelin@gmx•de> writes:
>> $ for i in {1,2,3,4,5}{0,1,2,3,4,5,6,7,8,9}; do echo $i; done
>> {1,2,3,4,5}{0,1,2,3,4,5,6,7,8,9}
>> $
>
> AFAIK this is the same as bash (I thought I was the last one to make that
> mistake 10 years ago). As long as you do not have _files_ matching the
> pattern, it does not expand. And besides, this is too complicated anyway:
> [1-5] is much shorter than {1,2,3,4,5}.
AFAIK, you are wrong ;-)
{1,2,3,4,5} expands regardless of what's on the filesystem but I
do not think it is POSIX.
[1-5] matches if any of the {1,2,3,4,5} is found on the
filesystem.
next prev parent reply other threads:[~2007-10-03 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-10-03 5:44 [PATCH] Must not modify the_index.cache as it may be passed to realloc at some point Keith Packard
2007-10-03 5:55 ` Junio C Hamano
2007-10-03 7:03 ` [PATCH] Add test case for ls-files --with-head Carl Worth
2007-10-03 12:09 ` Johannes Sixt
2007-10-03 15:36 ` Johannes Schindelin
2007-10-03 15:52 ` David Kastrup
2007-10-03 16:06 ` Carl Worth
2007-10-03 16:15 ` David Kastrup
2007-10-03 20:21 ` Jeff King
2007-10-03 21:39 ` Johannes Schindelin
2007-10-03 21:47 ` Junio C Hamano [this message]
2007-10-03 22:11 ` Jeff King
2007-10-03 19:29 ` Junio C Hamano
2007-10-03 15:50 ` Carl Worth
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=7vodffdg6i.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox$(echo .)com \
--cc=Johannes.Schindelin@gmx$(echo .)de \
--cc=cworth@cworth$(echo .)org \
--cc=git@vger$(echo .)kernel.org \
--cc=j.sixt@viscovery$(echo .)net \
--cc=keithp@keithp$(echo .)com \
--cc=peff@peff$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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