From: "Torsten Bögershausen" <tboegi@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2016, #04; Fri, 12)
Date: Mon, 15 Feb 2016 18:44:44 +0100 [thread overview]
Message-ID: <56C20E8C.30708@web.de> (raw)
In-Reply-To: <xmqqy4amr2z4.fsf@gitster.mtv.corp.google.com>
On 15/02/16 05:50, Junio C Hamano wrote:
> Torsten Bögershausen <tboegi@web.de> writes:
>
>>> * tb/conversion (2016-02-10) 6 commits
>>> (merged to 'next' on 2016-02-12 at 6faf27b)
>> Could we keep it in next for a while ?
>>
>> I found issues that needs to be fixed before going to master,
>> updates follow soonish.
> Hmph, I somehow thought that everything was a no-op clean-up. Any
> regressions I failed to spot?
The "text" attribute was reported incorrectly in ls-files --eol.
A preleminary fix is here:
<https://github.com/tboegi/git/commit/3a5f50005c0cfa16d2aaa6c602b6105b611a8ed5>
A proper fix will come next week.
next prev parent reply other threads:[~2016-02-15 17:45 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-12 23:50 What's cooking in git.git (Feb 2016, #04; Fri, 12) Junio C Hamano
2016-02-14 12:22 ` Torsten Bögershausen
2016-02-15 4:50 ` Junio C Hamano
2016-02-15 17:44 ` Torsten Bögershausen [this message]
2016-02-15 21:26 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=56C20E8C.30708@web.de \
--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.
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).