From: Derrick Stolee <stolee@gmail.com>
To: Johannes Sixt <j6t@kdbg.org>, Derrick Stolee <dstolee@microsoft.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH] t3705-add-sparse-checkout: ignore a LF->CRLF warning on Windows
Date: Tue, 18 Jan 2022 11:17:00 -0500 [thread overview]
Message-ID: <ea4cc086-744b-6fe5-08be-7a9c684da1a3@gmail.com> (raw)
In-Reply-To: <df42170b-8659-d496-3454-a4a3ac2827eb@kdbg.org>
On 1/15/2022 9:58 AM, Johannes Sixt wrote:
> There are checks that certain `git add` invocations do not produce
> output on stderr. One of them, the original one, uses
> "-c core.autocrlf=input" to ensure that `git add` does not write a
> hint about LF to CRLF conversion to stderr on Windows. A second
> `git add` was added in later patch, but it was forgotten to add
> the same protection. Add it now to let the test pass on Windows.
>
> Signed-off-by: Johannes Sixt <j6t@kdbg.org>
> ---
> Am 13.01.22 um 22:12 schrieb Johannes Sixt:
>> is there a reason we don't do this in the test case that you added in
>> 63b60b3add75 ("add: update --chmod to skip sparse paths", 2021-09-24).
>> Notice that the similar git add earlier also sets core.autocrlf.
>
> Here's a proper patch.
Thanks for this fix. I'm not sure why this fails on your Windows
machine but passes the Windows CI builds. Glad to have the fix
either way.
> - git add --sparse --chmod=+x sparse_entry 2>stderr &&
> + git -c core.autocrlf=input add --sparse --chmod=+x sparse_entry 2>stderr &&
Thanks,
-Stolee
next prev parent reply other threads:[~2022-01-18 16:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-13 21:12 Test failure on Windows in t3705-add-sparse-checkout.sh Johannes Sixt
2022-01-15 14:58 ` [PATCH] t3705-add-sparse-checkout: ignore a LF->CRLF warning on Windows Johannes Sixt
2022-01-18 16:17 ` Derrick Stolee [this message]
2022-01-16 3:58 ` Test failure on Windows in t3705-add-sparse-checkout.sh Elijah Newren
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=ea4cc086-744b-6fe5-08be-7a9c684da1a3@gmail.com \
--to=stolee@gmail.com \
--cc=dstolee@microsoft.com \
--cc=git@vger.kernel.org \
--cc=j6t@kdbg.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.
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).