From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [ANNOUNCE] Git v2.10.0-rc0
Date: Wed, 17 Aug 2016 06:42:45 +0000 [thread overview]
Message-ID: <20160817064245.GA5775@tb-raspi> (raw)
In-Reply-To: <xmqqoa4uhwcn.fsf@gitster.mtv.corp.google.com>
On Mon, Aug 15, 2016 at 08:42:48AM -0700, Junio C Hamano wrote:
> Torsten Bögershausen <tboegi@web.de> writes:
>
> > On 15.08.16 00:47, Junio C Hamano wrote:
> >> Torsten Bögershausen (1):
> >> convert: unify the "auto" handling of CRLF
> >
> > Should we mention this change in the release notes?
> >
> > The handling of "*.text = auto" was changed, and now
> >
> > $ echo "* text=auto eol=crlf" >.gitattributes
> > has the same effect as
> > $ git config core.autocrlf true
>
> Oh, definitely. Thanks.
Hm, one question remains:
git show 07c92928f2b782330df6e78
[]
+ * The handling of the "text = auto" attribute has been updated.
+ $ echo "* text=auto eol=crlf" >.gitattributes
+ used to have the same effect as
+ $ echo "* text=auto eol=crlf" >.gitattributes
Is this `text=auto` correct ?
I think it should be
used to have the same effect as
$ echo "* text eol=crlf" >.gitattributes
# In other words, the `auto` was ignored, as explained here:
+ $ git config core.eol crlf
+ i.e. declaring all files are text; the combination now is
+ equivalent to doing
+ $ git config core.autocrlf true
+
next prev parent reply other threads:[~2016-08-17 6:44 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-14 22:47 [ANNOUNCE] Git v2.10.0-rc0 Junio C Hamano
2016-08-15 13:59 ` Torsten Bögershausen
2016-08-15 15:42 ` Junio C Hamano
2016-08-17 6:42 ` Torsten Bögershausen [this message]
2016-08-17 15:33 ` Junio C Hamano
2016-08-17 17:38 ` Junio C Hamano
2016-08-17 18:27 ` Torsten Bögershausen
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=20160817064245.GA5775@tb-raspi \
--to=tboegi@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).