From: Jeff King <peff@peff.net>
To: Mike Ralphson <mike.ralphson@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH/RFD] builtin-revert.c: release index lock when cherry-picking an empty commit
Date: Sun, 22 Mar 2009 05:41:39 -0400 [thread overview]
Message-ID: <20090322094139.GA10599@coredump.intra.peff.net> (raw)
In-Reply-To: <e2b179460903110408i4ab3c9cg3c863b89a2f57cba@mail.gmail.com>
[this is a follow-up on the "eval 'false\n\n'" returns 0 issue on
FreeBSD]
On Wed, Mar 11, 2009 at 11:08:06AM +0000, Mike Ralphson wrote:
> 2009/3/11 Jeff King <peff@peff.net>:
> > OK, then nothing to worry about there. I have no idea which shell
> > OpenBSD and NetBSD use these days, and I don't have access to a box.
> > Anybody?
>
> OpenBSD uses pdksh in Bourne shell mode for non-root shells (ksh mode
> for root) [1].
>
> NetBSD >=4 uses a Bourne shell but I don't know the exact provenance.
> [2] "A sh command appeared in Version 1 AT&T UNIX. It was, however,
> unmaintainable so we wrote this one."
>
> [1] http://www.openbsd.org/faq/faq10.html#ksh
> [2] http://www.netbsd.org/docs/misc/index.html#shells
Thanks for looking this up, Mike. It sounds like FreeBSD is probably the
only problematic one. I confirmed that the problem still exists in
FreeBSD 7.1, and I've mailed the git ports maintainer off-list to
make him aware of the issue. So we'll see what happens.
Junio, do you want to put anything in the release notes warning people
who build from source that this is a potential issue? Do you want
something in the Makefile detecting that the shell is broken?
-Peff
next prev parent reply other threads:[~2009-03-22 9:43 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-07 9:30 [PATCH/RFD] builtin-revert.c: release index lock when cherry-picking an empty commit Chris Johnsen
2009-03-07 11:15 ` Johannes Schindelin
2009-03-07 22:57 ` Chris Johnsen
2009-03-08 1:19 ` Johannes Schindelin
2009-03-08 4:14 ` Junio C Hamano
2009-03-08 21:09 ` Chris Johnsen
2009-03-08 21:53 ` Junio C Hamano
2009-03-08 14:42 ` Jeff King
2009-03-08 15:09 ` Jeff King
2009-03-08 19:45 ` Junio C Hamano
2009-03-10 18:17 ` Jeff King
2009-03-10 18:25 ` Tomas Carnecky
2009-03-10 19:33 ` Tomas Carnecky
2009-03-10 23:57 ` Chris Johnsen
2009-03-11 0:30 ` Jeff King
2009-03-11 11:08 ` Mike Ralphson
2009-03-11 17:02 ` Mike Ralphson
2009-03-22 9:41 ` Jeff King [this message]
2009-03-22 21:58 ` Junio C Hamano
2009-03-22 22:38 ` Jeff King
2009-03-09 17:36 ` Brandon Casey
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=20090322094139.GA10599@coredump.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=mike.ralphson@gmail.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).