From: Thomas Berg <merlin66b@gmail.com>
To: Eyvind Bernhardsen <eyvind.bernhardsen@gmail.com>
Cc: Will Palmer <wmpalmer@gmail.com>, git@vger.kernel.org
Subject: Re: [BUG?] Fresh clone of jquery.git shows modifications?
Date: Wed, 18 Aug 2010 21:49:59 +0200 [thread overview]
Message-ID: <AANLkTik9yJjCEqPTB4K=FG8gBau7ADK3BGW-A7TaWFS2@mail.gmail.com> (raw)
In-Reply-To: <200088BC-F39D-407B-97ED-A771AA05E89D@gmail.com>
On Wed, Aug 18, 2010 at 9:19 PM, Eyvind Bernhardsen
<eyvind.bernhardsen@gmail.com> wrote:
> On 18. aug. 2010, at 17.50, Thomas Berg wrote:
>> Maybe there is a better way?
>
> There may be, but I'm not sure it would be worth the effort. The reason I started working on CRLF normalization in the first place was because I got tired of seeing spuriously modified files everywhere when using core.autocrlf, so I know how annoying it is. The difference now is that only people using "mis-attributed" repositories are annoyed, instead of anyone who uses core.autocrlf, and as I wrote elsewhere, I don't expect there to be many repositories where this is a problem.
I guess you're right, probably not worth the effort (although I think
that the spuriously modified files are just as "bad" in this case).
Thanks a lot for your work on this, it scratched all my CRLF itches at
least.
I'm maintaining my own personal patches on top of quite a few git-svn
mirrors and git-hg mirrors. Before git 1.7.2, rebasing these on
Windows was a pain. I even maintained my own .gitattributes files for
many of them, but still had problems. Now all is solved!
- Thomas
next prev parent reply other threads:[~2010-08-18 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-08-18 12:40 [BUG?] Fresh clone of jquery.git shows modifications? Will Palmer
2010-08-18 13:18 ` Eyvind Bernhardsen
2010-08-18 14:14 ` Will Palmer
2010-08-18 15:50 ` Thomas Berg
2010-08-18 16:37 ` Will Palmer
2010-08-18 18:09 ` Eyvind Bernhardsen
2010-08-18 19:19 ` Eyvind Bernhardsen
2010-08-18 19:49 ` Thomas Berg [this message]
2010-08-18 18:55 ` Eyvind Bernhardsen
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='AANLkTik9yJjCEqPTB4K=FG8gBau7ADK3BGW-A7TaWFS2@mail.gmail.com' \
--to=merlin66b@gmail.com \
--cc=eyvind.bernhardsen@gmail.com \
--cc=git@vger.kernel.org \
--cc=wmpalmer@gmail.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.
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).