git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@github.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Josh Stone <jistone@redhat.com>, git@vger.kernel.org
Subject: Re: [PATCH] blame: Improve parsing for emails with spaces
Date: Fri, 29 Apr 2011 15:13:55 -0400	[thread overview]
Message-ID: <20110429191355.GC27268@sigill.intra.peff.net> (raw)
In-Reply-To: <7vvcxxvsz4.fsf@alter.siamese.dyndns.org>

On Fri, Apr 29, 2011 at 10:59:43AM -0700, Junio C Hamano wrote:

> > Hmm. That address seems bogus, and I wonder if we should be rejecting it
> > at commit time. Still, it is something we may run across in existing
> > repositories, so handling it more gracefully makes sense.
> 
> Perhaps but within reason.  
> 
> What new types of breakages are we proposing to tolerate, what breakages
> are we declaring not worth fixing, and what is the price of not loosening
> this?  Without this patch, such a broken commit will result in the author
> email shown somewhat broken, but the original is already broken to begin
> with, and also the entry for the blamed line will come with its commit
> object name anyway, so I do not think it is such a big deal.

I'm pretty sure such an address would make a non-rfc822-compliant "from"
header when used with format-patch. But given that it is obviously a
bogus address, I don't think there's much we can do anyway, and anyone
looking at will say "Oh, that's wrong". So it's probably not a big deal.

-Peff

      parent reply	other threads:[~2011-04-29 19:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-21 22:07 [PATCH] blame: Improve parsing for emails with spaces Josh Stone
2011-04-29 13:11 ` Jeff King
2011-04-29 17:59   ` Junio C Hamano
2011-04-29 18:09     ` Junio C Hamano
2011-04-29 18:17     ` Josh Stone
2011-04-29 19:13     ` Jeff King [this message]

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=20110429191355.GC27268@sigill.intra.peff.net \
    --to=peff@github.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=jistone@redhat.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).