From: Thomas Rast <trast@student.ethz.ch>
To: Vitali <vit.der.kapa@gmx.com>
Cc: <git@vger.kernel.org>
Subject: Re: blame formatting bug
Date: Thu, 9 Dec 2010 14:55:49 +0100 [thread overview]
Message-ID: <201012091455.50144.trast@student.ethz.ch> (raw)
In-Reply-To: <4D008F3A.7080205@gmx.com>
Vitali wrote:
> df9c37ec jquery/jquery.js (John Resig 2006-07-09 20:49:40 +0000 578)
> extend: function(obj,prop) {
> if ( !prop ) {
> prop = obj;
> obj = this;
> }
>
> for ( var i in prop )
> obj[i] = prop[i];
>
> return obj;
> }
>
> Looks like bug.
My 'less' shows that these lines are "terminated" with CRs. Git's
diff engine does not treat CRs as line endings, so neither does blame.
--
Thomas Rast
trast@{inf,student}.ethz.ch
prev parent reply other threads:[~2010-12-09 13:55 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-12-09 8:11 blame formatting bug Vitali
2010-12-09 13:55 ` Thomas Rast [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=201012091455.50144.trast@student.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=vit.der.kapa@gmx.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).