From: Mike Ralphson <mike.ralphson@gmail.com>
To: Jeff King <peff@peff.net>
Cc: Chris Johnsen <chris_johnsen@pobox.com>,
Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Miklos Vajna <vmiklos@frugalware.org>
Subject: Re: [PATCH/RFD] builtin-revert.c: release index lock when cherry-picking an empty commit
Date: Wed, 11 Mar 2009 17:02:04 +0000 [thread overview]
Message-ID: <e2b179460903111002p195628ddka23529d898a2ec1f@mail.gmail.com> (raw)
In-Reply-To: <e2b179460903110408i4ab3c9cg3c863b89a2f57cba@mail.gmail.com>
2009/3/11 Mike Ralphson <mike.ralphson@gmail.com>
>
> 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)
... and isn't broken in this instance (OpenBSD v4.1)
Weird test failures though, so now I'm looking at that 8-)
next prev parent reply other threads:[~2009-03-11 17:04 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 [this message]
2009-03-22 9:41 ` Jeff King
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=e2b179460903111002p195628ddka23529d898a2ec1f@mail.gmail.com \
--to=mike.ralphson@gmail.com \
--cc=chris_johnsen@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.net \
--cc=vmiklos@frugalware.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;
as well as URLs for NNTP newsgroup(s).