git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Lanny Ripple <lanny@spotinfluence.com>
Cc: Junio C Hamano <gitster@pobox.com>,
	Thomas Rast <trast@inf.ethz.ch>,
	git@vger.kernel.org
Subject: Re: Bug: rebase when an author uses accents in name on MacOSx
Date: Sat, 2 Jun 2012 12:09:04 -0400	[thread overview]
Message-ID: <20120602160904.GB15017@sigill.intra.peff.net> (raw)
In-Reply-To: <B0BB0BD8-EFB5-4A3C-A6F7-00A1C7DE0509@spotinfluence.com>

On Fri, Jun 01, 2012 at 08:56:01AM -0500, Lanny Ripple wrote:

> I did show that sed was broken and have provided a minimal, reproducible test.
> 
> I have reported it to the sed maintainers and they are working on it.

Great. Do we know yet which versions are affected?

> A message or comment in the code that seds not properly handling utf8
> characters have been shown to be the cause of the problem and that git
> selects sed from the PATH would have been 100% effective in at least
> one case.  I don't know the troubleshooting skills of the other two
> people that bumped into the problem so can't comment.  Of the billions
> of people that have not (if it existed) looked at the breadcrumb and
> weren't led astray it's (would have) also been 100% effective.  Can
> you in turn posit any reasonable way that get_author_ident_from_commit
> would improperly build author-script short of a bad sed?  I guess you
> could pull out transient or systematic disk error.

I assume from bogus commit objects. But I admit I am just guessing, and
don't have data.

> You do, in fact, have several solutions.  I won't reiterate since they
> are in the thread earlier.  You also have in many cases the valid
> concern that the solutions would not be backwards compatible.  And
> yes, this sed will get fixed but what then?  The next person that gets
> a sed they don't expect earlier in their PATH will have to go through
> the same steps.

When I said:

> > But really, I'd rather just see the broken sed fixed. Where would the
> > breadcrumb lead people at this point, anyway? We don't actually have a
> > solution besides "uninstall this other, crappy sed". Has the sed bug
> > actually been fixed?

I meant that there is not a fix for the _user_ to perform at that point.
The point of a breadcrumb like that is that we are not going to put a
fix into git, so we want to at least give the user a clue that their
system has a problem. But what is their next step after being informed
that their system has a problem?

-Peff

  reply	other threads:[~2012-06-02 16:09 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-05-30 22:16 Bug: rebase when an author uses accents in name on MacOSx Lanny Ripple
2012-05-30 23:45 ` Junio C Hamano
2012-05-30 23:57   ` Jürgen Kreileder
2012-05-31  1:19   ` Jeff King
2012-05-31  6:33     ` Junio C Hamano
2012-05-31 13:36       ` Lanny Ripple
2012-05-31 14:28         ` Thomas Rast
2012-05-31 14:56           ` Lanny Ripple
2012-05-31 17:34         ` Junio C Hamano
2012-05-31 17:49           ` Lanny Ripple
2012-05-31 18:33             ` Junio C Hamano
2012-05-31 19:21               ` Lanny Ripple
2012-06-01  9:30                 ` Jeff King
2012-06-01 13:56                   ` Lanny Ripple
2012-06-02 16:09                     ` Jeff King [this message]
2012-06-02 16:37                       ` Lanny Ripple
2012-06-01 16:19                   ` Junio C Hamano
2012-06-01 17:05                     ` Lanny Ripple
2012-06-01 17:57                       ` Junio C Hamano
2012-06-02 16:23                     ` Jeff King
2012-05-31  9:33     ` Thomas Rast

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=20120602160904.GB15017@sigill.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=lanny@spotinfluence.com \
    --cc=trast@inf.ethz.ch \
    /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).