From: Felipe Contreras <felipe.contreras@gmail.com>
To: Jeff King <peff@peff.net>
Cc: "Magnus Bäck" <baeck@google.com>,
"Michael Haggerty" <mhagger@alum.mit.edu>,
"Eric S. Raymond" <esr@thyrsus.com>,
git@vger.kernel.org
Subject: Re: Python extension commands in git - request for policy change
Date: Wed, 28 Nov 2012 03:06:09 +0100 [thread overview]
Message-ID: <CAMP44s1jzUWm8BKxJR29RNWTWnxReExTeDTAKhk3mF3WJYNE0w@mail.gmail.com> (raw)
In-Reply-To: <20121128013943.GA23776@sigill.intra.peff.net>
On Wed, Nov 28, 2012 at 2:39 AM, Jeff King <peff@peff.net> wrote:
> On Wed, Nov 28, 2012 at 02:22:09AM +0100, Felipe Contreras wrote:
>
>> Sure, you will argue that we don't see the *real* issues, because they
>> were fixed preemptively, but the fact of the matter is that we will
>> never know. All we know is the reality we can observe, and the reality
>> is that we hit very few *real* issues outside the test system (feel
>> free to provide evidence to the contrary).
>
> I think reports of breakage in the test scripts are relevant, because
> they are indicative that people _do_ run platforms that care about these
> issues, and if we were to write a lot of shell scripts, we would run
> across them more frequently. But the fact of the matter is that we don't
> write a lot of non-test shell scripts these days, which is part of the
> reason limiting your search to the last 2 years did not turn up many
> fixes outside the tests.
If we were to write a lot of shell scripts, and we were to apply the
same standards as we do with the tests, which most likely wouldn't be
the case; end-user scripts are way more important, specially
porcelain.
> There was a big push in 2006 and 2007 to port some of the hairier
> scripts to C. Try:
>
> git log --no-renames --diff-filter=D \
> --diff-filter=D --format='%ad %s' --date=short \
> -- 'git-*.sh'
>
> A lot of it was motivated by portability and decent performance for
> common commands under Windows.
Good stuff indeed. I look forward to the day all main git porcelain
commands are written in C (git-rebase I'm looking at you), there are
not many left:
git-am
git-bisect
git-citool
git-gui
git-pull
git-rebase
git-stash
git-submodule
> Anyway, there is not much point in debating the exact level of pain that
> shell portability causes us. Even if you accept that there is some, it
> is clearly not a major problem for the project.
Indeed.
--
Felipe Contreras
next prev parent reply other threads:[~2012-11-28 2:06 UTC|newest]
Thread overview: 82+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-25 2:44 Python extension commands in git - request for policy change Eric S. Raymond
2012-11-25 3:15 ` Nguyen Thai Ngoc Duy
2012-11-25 5:18 ` Eric S. Raymond
2012-11-25 8:56 ` Felipe Contreras
2012-11-25 9:54 ` Eric S. Raymond
2012-11-25 11:48 ` Felipe Contreras
2012-11-25 17:50 ` Eric S. Raymond
2012-11-25 21:22 ` Felipe Contreras
2012-11-25 21:56 ` Eric S. Raymond
2012-11-26 13:11 ` Felipe Contreras
2012-11-27 7:54 ` David Aguilar
2012-11-27 8:43 ` Felipe Contreras
2012-11-27 9:17 ` Sitaram Chamarty
2012-11-27 10:51 ` David Aguilar
2012-11-27 22:01 ` Guillaume DE BURE
2012-11-27 15:33 ` Johannes Schindelin
2012-11-28 2:09 ` Felipe Contreras
2012-11-25 17:21 ` Johannes Schindelin
2012-11-25 10:26 ` Pat Thoyts
2012-11-25 10:33 ` Eric S. Raymond
2012-11-25 15:51 ` Erik Faye-Lund
2012-11-25 8:53 ` Felipe Contreras
2012-11-25 9:53 ` Eric S. Raymond
2012-11-25 11:19 ` Felipe Contreras
2012-11-25 17:32 ` Eric S. Raymond
2012-11-25 21:43 ` Felipe Contreras
2012-11-25 22:44 ` Eric S. Raymond
2012-11-26 11:05 ` Andreas Ericsson
2012-11-25 10:44 ` Michael Haggerty
2012-11-25 10:57 ` Eric S. Raymond
2012-11-25 11:51 ` David Lang
2012-11-25 12:01 ` Stefano Lattarini
2012-11-25 17:44 ` Eric S. Raymond
2012-11-25 11:25 ` Nguyen Thai Ngoc Duy
2012-12-11 5:44 ` Patrick Donnelly
2012-12-12 0:09 ` Sitaram Chamarty
2012-12-12 0:28 ` Patrick Donnelly
2012-12-12 0:53 ` Tomas Carnecky
2012-12-12 1:50 ` Nguyen Thai Ngoc Duy
2012-12-12 2:22 ` Tomas Carnecky
2012-12-12 2:26 ` Patrick Donnelly
2012-12-12 5:15 ` Joshua Jensen
2012-12-12 3:30 ` Eric S. Raymond
2012-12-12 5:11 ` Joshua Jensen
2012-12-12 12:23 ` Eric S. Raymond
2012-12-12 6:32 ` Jeff King
2012-12-12 7:03 ` Patrick Donnelly
2012-12-12 8:32 ` Jeff King
2012-12-12 12:26 ` Eric S. Raymond
2012-12-12 12:29 ` Jeff King
2012-12-12 17:49 ` Junio C Hamano
2012-12-12 22:21 ` Andrew Ardill
2012-12-12 22:43 ` Junio C Hamano
2012-12-12 7:11 ` Patrick Donnelly
2012-12-12 12:43 ` Eric S. Raymond
2012-12-19 2:30 ` Patrick Donnelly
2012-11-25 11:40 ` Felipe Contreras
2012-11-25 17:36 ` Eric S. Raymond
2012-11-25 21:25 ` Felipe Contreras
2012-11-25 22:11 ` Eric S. Raymond
2012-11-26 13:17 ` Felipe Contreras
2012-11-27 14:35 ` Magnus Bäck
2012-11-27 18:35 ` Eric S. Raymond
2012-11-27 21:08 ` Sitaram Chamarty
2012-11-28 0:16 ` Felipe Contreras
2012-12-03 21:45 ` Philippe Vaucher
2012-12-04 14:19 ` Felipe Contreras
2012-12-04 14:40 ` Stephen Bash
2012-11-28 0:10 ` Felipe Contreras
2012-11-28 0:51 ` Jeff King
2012-11-28 1:22 ` Felipe Contreras
2012-11-28 1:39 ` Jeff King
2012-11-28 2:06 ` Felipe Contreras [this message]
2012-11-28 15:39 ` Magnus Bäck
2012-11-28 5:08 ` Joshua Jensen
2012-11-25 8:57 ` Johannes Sixt
2012-11-25 10:25 ` Eric S. Raymond
2012-11-25 21:41 ` Krzysztof Mazur
2012-11-25 22:47 ` Eric S. Raymond
2012-11-26 5:10 ` Sitaram Chamarty
2012-11-26 8:32 ` Krzysztof Mazur
2012-12-04 15:51 ` Martin Langhoff
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=CAMP44s1jzUWm8BKxJR29RNWTWnxReExTeDTAKhk3mF3WJYNE0w@mail.gmail.com \
--to=felipe.contreras@gmail.com \
--cc=baeck@google.com \
--cc=esr@thyrsus.com \
--cc=git@vger.kernel.org \
--cc=mhagger@alum.mit.edu \
--cc=peff@peff.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).