From: Stephan Beyer <s-beyer@gmx.net>
To: Johannes Schindelin <Johannes.Schindelin@gmx.de>
Cc: Johannes Sixt <j.sixt@viscovery.net>,
git@vger.kernel.org, Christian Couder <chriscool@tuxfamily.org>
Subject: Re: [PATCH 2/3] rebase-i: slight internal improvements
Date: Fri, 20 Jun 2008 20:45:03 +0200 [thread overview]
Message-ID: <20080620184503.GD7369@leksak.fem-net> (raw)
In-Reply-To: <alpine.DEB.1.00.0806201344180.6439@racer>
On Fri, Jun 20, 2008 at 01:46:29PM +0100, Johannes Schindelin <Johannes.Schindelin@gmx.de> wrote to Cc git@vger.kernel.org:
> Hi,
>
> On Fri, 20 Jun 2008, Stephan Beyer wrote:
>
> > Looks like *portable* shell programming is no fun :\
>
> That is right. That's one of the reasons why I prefer moving scripts to
> builtins: prototyping is good and well, but when you need to put it into
> production, where people have all kinds of weird setups
Right.
> (just think of dash in Ubuntu!)
Well, I'm using dash as /bin/sh in Debian.
What's so weird about it? IIRC it allows POSIX + some Berkeley extensions
and so it is far less weird as the least common demoninator of shell
portability ;-)
Hmm,
For shell portability it'd be cool to have something like a "badsh" (bad
shell) with the whole XCU Utilities as builtins without features and
warnings if features want to be used that are not supported by at least
95% of the systems. So that scripts could be checked using badsh and
then you know, that it is portable.
I guess nobody ever wrote something like that. ;-)
> Better to use something portable, such as C.
Right.
> So would you not agree that PATCH 2/3 is rather unnecessary?
We wanted to make some upfront patches to am/rebase-i, so that, when the
git-sequencer prototype swoops in, it's easier to see, what is
taken from am and what is taken from rebase-i.
But this seems to be not so easy, so I'm currently thinking that I skip
that and concentrate on the builtin.
Regards,
Stephan
--
Stephan Beyer <s-beyer@gmx.net>, PGP 0x6EDDD207FCC5040F
next prev parent reply other threads:[~2008-06-20 18:46 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-20 2:45 some small changes for rebase-i Stephan Beyer
2008-06-20 2:45 ` [PATCH 1/3] t3404: slight improvements Stephan Beyer
2008-06-20 2:45 ` [PATCH 2/3] rebase-i: slight internal improvements Stephan Beyer
2008-06-20 2:45 ` [PATCH 3/3] Make rebase--interactive use OPTIONS_SPEC Stephan Beyer
2008-06-20 5:48 ` Stephan Beyer
2008-06-20 13:15 ` Johannes Schindelin
2008-06-20 18:30 ` [PATCH 1/2] t3404: extra checks and s/! git/test_must_fail git/ Stephan Beyer
2008-06-20 18:30 ` [PATCH 2/2] Make rebase--interactive use OPTIONS_SPEC Stephan Beyer
2008-06-20 18:48 ` [PATCH 1/2] t3404: extra checks and s/! git/test_must_fail git/ Brandon Casey
2008-06-20 19:00 ` Stephan Beyer
2008-06-20 22:18 ` しらいしななこ
2008-06-21 1:46 ` Stephan Beyer
2008-06-21 9:46 ` Junio C Hamano
2008-06-21 23:55 ` [PATCH v3 1/2] t3404: stricter tests for git-rebase--interactive Stephan Beyer
2008-06-21 23:55 ` [PATCH v3 2/2] Make rebase--interactive use OPTIONS_SPEC Stephan Beyer
2008-06-20 7:16 ` [PATCH 2/3] rebase-i: slight internal improvements Johannes Sixt
2008-06-20 8:01 ` Stephan Beyer
2008-06-20 8:17 ` Johannes Sixt
2008-06-20 12:46 ` Johannes Schindelin
2008-06-20 18:45 ` Stephan Beyer [this message]
2008-06-20 13:05 ` [PATCH 1/3] t3404: slight improvements Johannes Schindelin
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=20080620184503.GD7369@leksak.fem-net \
--to=s-beyer@gmx.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
/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).