From: "Hnerik Grubbström" <grubba@grubba.org>
To: git@vger.kernel.org
Subject: Re: [PATCH v2] autocrlf: Make it work also for un-normalized repositories
Date: Wed, 12 May 2010 09:26:06 +0000 (UTC) [thread overview]
Message-ID: <loom.20100512T112040-607@post.gmane.org> (raw)
In-Reply-To: 20100511223757.GB16974@pvv.org
Finn Arne Gangstad <finnag <at> pvv.org> writes:
> Previously, autocrlf would only work well for normalized
> repositories. Any text files that contained CRLF in the repository
> would cause problems, and would be modified when handled with
> core.autocrlf set.
>
> The following sequence should now always be a NOP even with autocrlf
> set (assuming a clean working directory):
>
> git checkout <something>
> touch *
> git add -A . (will add nothing)
> git commit (nothing to commit)
Please note that the above problem is solved for the general case with the
"[PATCH v3 0/5] Patches to avoid reporting conversion changes." patch set.
--
/grubba
next prev parent reply other threads:[~2010-05-12 10:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-11 22:37 [PATCH v2] autocrlf: Make it work also for un-normalized repositories Finn Arne Gangstad
2010-05-12 6:16 ` Dmitry Potapov
2010-05-12 6:33 ` Eyvind Bernhardsen
2010-05-12 9:26 ` Hnerik Grubbström [this message]
2010-05-23 9:30 ` Clemens Buchacher
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=loom.20100512T112040-607@post.gmane.org \
--to=grubba@grubba.org \
--cc=git@vger.kernel.org \
/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).