From: Jakub Narebski <jnareb@gmail.com>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 2/3] git-fetch: do not use "*" for fetching multiple refs
Date: Thu, 7 Dec 2006 00:38:24 +0100 [thread overview]
Message-ID: <200612070038.24920.jnareb@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.63.0612070020580.28348@wbgn013.biozentrum.uni-wuerzburg.de>
Johannes Schindelin wrote:
> On Wed, 6 Dec 2006, Jakub Narebski wrote:
>
>> Michael Loeffler wrote:
>>
>>> Am Montag, den 04.12.2006, 20:48 +0100 schrieb Jakub Narebski:
>>> ...
>>>> I'm not sure if regexp support is truly better than the usual path globbing,
>>>> as in fnmatch / glob.
>>>
>>> The current code does not do a real glob, this was the reason for me to
>>> think about regex support, I thought it is easy to use sed for this. Now
>>> I know it better.
>>
>> We could use perl for that, but embedded perl is a bit horrible.
>
> Not to talk about portable, and as we saw, dependent on the C compiler
> (you would have to make git compile with the same C compiler that perl was
> compiled with).
>
> So, please look into other options first.
No, not embedded in C, but embedded in shell script.
Use perl -ip instead of sed.
--
Jakub Narebski
next prev parent reply other threads:[~2006-12-06 23:36 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-04 19:38 [PATCH 2/3] git-fetch: do not use "*" for fetching multiple refs Michael Loeffler
2006-12-04 19:48 ` Jakub Narebski
2006-12-06 16:34 ` Michael Loeffler
2006-12-06 16:58 ` Jakub Narebski
2006-12-06 18:16 ` Michael Loeffler
2006-12-06 18:27 ` Jakub Narebski
2006-12-06 18:39 ` Junio C Hamano
2006-12-06 18:37 ` Junio C Hamano
2006-12-06 23:21 ` Johannes Schindelin
2006-12-06 23:38 ` Jakub Narebski [this message]
2006-12-04 19:49 ` Michael Loeffler
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=200612070038.24920.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.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 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.