git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Robert Schiele <rschiele@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: David Kastrup <dak@gnu.org>, git@vger.kernel.org
Subject: Re: Shell script cleanups/style changes?
Date: Fri, 3 Aug 2007 01:21:27 +0200	[thread overview]
Message-ID: <20070802232126.GU29424@schiele.dyndns.org> (raw)
In-Reply-To: <7vwswdsfjp.fsf@assigned-by-dhcp.cox.net>

[-- Attachment #1: Type: text/plain, Size: 694 bytes --]

On Thu, Aug 02, 2007 at 04:05:46PM -0700, Junio C Hamano wrote:
> However, there is a line we need to draw when bending bacwards
> for compatibility, and I think a system that does not have a
> working command substitution $( ... )  is on the other side of
> that line.

Well, I have now a patch ready for submission that would replace all
occurences of ${PARAMETER#WORD}, ${PARAMETER%WORD}, and $(( EXPRESSION )).
But if you say that you won't accept replacement of $( ... ) then this is not
worth the effort since this one isn't accepted as well.

Robert

-- 
Robert Schiele
Dipl.-Wirtsch.informatiker	mailto:rschiele@gmail.com

"Quidquid latine dictum sit, altum sonatur."

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

  parent reply	other threads:[~2007-08-02 23:21 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02 10:44 Shell script cleanups/style changes? David Kastrup
2007-08-02 14:00 ` Robert Schiele
2007-08-02 14:20   ` David Kastrup
2007-08-02 16:19     ` Robert Schiele
2007-08-02 17:05       ` Johannes Schindelin
2007-08-02 17:22         ` Robert Schiele
2007-08-03 19:29     ` Uwe Kleine-König
2007-08-02 14:48 ` Bradford Smith
2007-08-02 18:13   ` Sam Ravnborg
2007-08-02 20:37 ` Junio C Hamano
2007-08-02 20:56   ` Nguyen Thai Ngoc Duy
2007-08-02 21:02     ` David Kastrup
2007-08-02 21:12     ` Junio C Hamano
2007-08-02 20:57   ` David Kastrup
2007-08-02 21:21     ` Junio C Hamano
2007-08-02 21:29       ` Junio C Hamano
2007-08-02 22:02         ` David Kastrup
2007-08-02 21:41       ` Robert Schiele
2007-08-02 22:14         ` David Kastrup
2007-08-02 23:05           ` Junio C Hamano
2007-08-02 23:17             ` David Kastrup
2007-08-03  0:12               ` Junio C Hamano
2007-08-03  0:24                 ` David Kastrup
2007-08-03  0:48                   ` Junio C Hamano
2007-08-03  6:06                     ` David Kastrup
2007-08-03  7:41                       ` Junio C Hamano
2007-08-03  8:41                         ` David Kastrup
2007-08-03  6:13                     ` David Kastrup
2007-08-03  2:28                   ` Robert Schiele
2007-08-03  6:08                     ` David Kastrup
2007-08-02 23:21             ` Robert Schiele [this message]
2007-08-02 23:32               ` David Kastrup
2007-08-02 23:45                 ` Robert Schiele
2007-08-02 23:52                   ` David Kastrup
2007-08-03  0:01                     ` Robert Schiele
2007-08-03  0:11                       ` David Kastrup
2007-08-03  7:11                         ` Junio C Hamano
2007-08-02 23:27           ` Robert Schiele
2007-08-04  7:10         ` Florian Weimer
2007-08-04 20:32           ` Robert Schiele
2007-08-04 20:39             ` Junio C Hamano
2007-08-02 21:42       ` David Kastrup

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=20070802232126.GU29424@schiele.dyndns.org \
    --to=rschiele@gmail.com \
    --cc=dak@gnu.org \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).