From: George Shapovalov <george@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: gnustep-base.eclass
Date: Fri, 05 Oct 2007 20:50:59 +0200 [thread overview]
Message-ID: <200710052051.00219.george@gentoo.org> (raw)
In-Reply-To: <20071005180356.GK29572@supernova>
Friday, 5. October 2007, Donnie Berkholz Ви написали:
> There's gotta be a better way of doing this. All those escapes really
> start to obfuscate the code. Anyone got a better idea?
Just use single quotes? This should prevent bash expansion.
Although, as I can see, this is done in here-function, so it is better to test
first (which is a good idea in any case :)), but I don't see right away why
that would not work..
George
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2007-10-05 19:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Idkm9-0003dm-4y@stork.gentoo.org>
2007-10-05 18:03 ` [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in eclass: gnustep-base.eclass Donnie Berkholz
2007-10-05 18:12 ` Fabian Groffen
2007-10-05 18:50 ` George Shapovalov [this message]
2007-10-05 19:47 ` Roy Marples
2007-10-05 23:31 ` Ryan Hill
2007-10-06 0:08 ` Donnie Berkholz
2007-10-07 22:43 ` Bernard Cafarelli
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=200710052051.00219.george@gentoo.org \
--to=george@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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