From: Junio C Hamano <gitster@pobox.com>
To: "Torsten Bögershausen" <tboegi@web.de>
Cc: git@vger.kernel.org
Subject: Re: [PATCH 1/2] t0027: Tests for core.eol=native, eol=lf, eol=crlf
Date: Thu, 28 Aug 2014 12:20:56 -0700 [thread overview]
Message-ID: <xmqqha0wa09z.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <53EFBC3A.5020805@web.de> ("Torsten Bögershausen"'s message of "Sat, 16 Aug 2014 22:16:58 +0200")
Torsten Bögershausen <tboegi@web.de> writes:
> Add test cases for core.eol "native" and "" (unset).
> (MINGW uses CRLF, all other systems LF as native line endings)
>
> Add test cases for the attributes "eol=lf" and "eol=crlf"
>
> Other minor changes:
> - Use the more portable 'tr' instead of 'od -c' to convert '\n' into 'Q'
> and '\0' into 'N'
> - Style fixes for shell functions according to the coding guide lines
> - Replace "txtbin" with "attr"
>
> Signed-off-by: Torsten Bögershausen <tboegi@web.de>
> ---
It appears that I missed this patch? You seem to have rerolled the
corresponding 2/2, to which I responded ($gmane/255507). Is this
one still viable/necessary?
If you are doing the whole-sale style fixes for this script, can you
also fix the case/esac statement in create_gitattributes? The case
arm labels are indented one level too deep, making it harder to spot
them than necessary.
Test files "setup master" step creates appear to end in an
incomplete line. Is this intended or by mistake? Making sure
things work even on files that end in an incomplete line is a good
thing, but it looks somewhat strange not to test normal cases (in
other words, it makes it appear as if normal cases work OK but
incomplete lines cause corner case bugs and these tests are meant to
check them, or something).
Thanks.
next prev parent reply other threads:[~2014-08-28 19:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-16 20:16 [PATCH 1/2] t0027: Tests for core.eol=native, eol=lf, eol=crlf Torsten Bögershausen
2014-08-28 19:20 ` Junio C Hamano [this message]
2014-08-30 9:01 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=xmqqha0wa09z.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=tboegi@web.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.