From: Junio C Hamano <gitster@pobox.com>
To: "Jason Pyeron" <jpyeron@pdinc.us>
Cc: <git@vger.kernel.org>
Subject: Re: Blame / annotate with mixed mac line endings?
Date: Thu, 03 May 2018 10:22:01 +0900 [thread overview]
Message-ID: <xmqqh8npv8hy.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <B8114616E07247C7A78F1DFF91E16A63@ad.pdinc.us> (Jason Pyeron's message of "Wed, 2 May 2018 19:57:28 -0400")
"Jason Pyeron" <jpyeron@pdinc.us> writes:
> Any way to hit git with a stick to treat lone CR as a line break for blame/annotate?
I highly suspect that you would get more help from those whose love
is Git if your inquiry were about a way to ask Git politely to do
what you want to achieve, rather than hitting it with a stick ;-)
Perhaps define a textconv filter to fix the incorrect line endings?
That way, you do not have to rewrite the history only to run blame,
but can pretend as if the contents were all using consistent line
endings (either LF or CRLF) retroactively.
next prev parent reply other threads:[~2018-05-03 1:22 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-02 23:57 Blame / annotate with mixed mac line endings? Jason Pyeron
2018-05-03 1:22 ` Junio C Hamano [this message]
2018-05-03 2:32 ` Jason Pyeron
2018-05-03 4:55 ` Junio C Hamano
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqh8npv8hy.fsf@gitster-ct.c.googlers.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jpyeron@pdinc.us \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).