From: Jeff King <peff@peff.net>
To: Olivier ROLAND <cyrus-dev@edla.org>
Cc: git@vger.kernel.org
Subject: Re: Bug report : bad filter-branch (OSX only)
Date: Wed, 29 Apr 2015 00:39:47 -0400 [thread overview]
Message-ID: <20150429043947.GA10702@peff.net> (raw)
In-Reply-To: <CAM=W1NnR2-T7vpMSM-3-VypnR-T235tMudyjJowtj5utNmoKNQ@mail.gmail.com>
On Tue, Apr 28, 2015 at 01:02:17PM +0200, Olivier ROLAND wrote:
> Both versions are builded from source.
> head -1 "$(git --exec-path)/git-filter-branch"
> #!/bin/sh
>
> sh --version
> GNU bash, version 3.2.57(1)-release (x86_64-apple-darwin14)
> Copyright (C) 2007 Free Software Foundation, Inc.
>
> /bin/bash --version
> GNU bash, version 4.1.5(1)-release (x86_64-pc-linux-gnu)
>
> The bug seem really git related.
Yes, but I guessed it might be part of the filter-branch shell script
that behaves differently under two different shells (i.e., that we used
some unportable construct). However, I built bash 3.2.57 on my Linux box
and could not replicate the problem.
The other "usual" thing that causes bugs to show up on OS X but not
Linux is case-folding. But you said you are using a case-sensitive
filesystem, so it's probably not that.
So I can't figure out how to replicate the problem here.
-Peff
next prev parent reply other threads:[~2015-04-29 4:39 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-26 9:25 Bug report : bad filter-branch (OSX only) Olivier ROLAND
2015-04-28 5:55 ` Jeff King
2015-04-28 11:02 ` Olivier ROLAND
2015-04-29 4:39 ` Jeff King [this message]
2015-04-29 4:56 ` Jeff King
2015-04-29 5:39 ` Junio C Hamano
2015-04-29 15:48 ` Jeff King
2015-04-29 16:30 ` Junio C Hamano
2015-04-29 16:43 ` Jeff King
2015-04-29 17:13 ` Junio C Hamano
2015-04-29 18:17 ` Johannes Sixt
2015-04-29 14:42 ` Roberto Tyley
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=20150429043947.GA10702@peff.net \
--to=peff@peff.net \
--cc=cyrus-dev@edla.org \
--cc=git@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.