From: Junio C Hamano <gitster@pobox.com>
To: Patrick Steinhardt <ps@pks.im>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] whitespace: symbolic links usually lack LF at the end
Date: Thu, 05 Feb 2026 07:50:55 -0800 [thread overview]
Message-ID: <xmqqms1nmbog.fsf@gitster.g> (raw)
In-Reply-To: <aYSLP1LqBiMwur3O@pks.im> (Patrick Steinhardt's message of "Thu, 5 Feb 2026 13:21:19 +0100")
Patrick Steinhardt <ps@pks.im> writes:
> I'd suggest that we only disable this check in case either:
>
> - One side doesn't exist, the other is a symbolic link.
>
> - Both sides are a symbolic link.
Hmm. That is indeed a thoguht. But we do not want to complain in
text-to-symlink transition that postimage lacks the terminating LF,
so the above rules may be a good start but will need further
tweaking, I am afraid.
> Another question is whether we support symref targets that end in a
> newline. I guess the answer is going to be some form of "yes", and in
> that case we could of course loose some information. But honestly, this
> is so much of an edge case that I don't really worry about it too much.
Do we track, apply and diff any symrefs? I thought that we do not
touch anything inside .git/ and symrefs live inside .git/refs/
(except for .git/HEAD)?
next prev parent reply other threads:[~2026-02-05 15:50 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-04 21:23 [PATCH] whitespace: symbolic links usually lack LF at the end Junio C Hamano
2026-02-05 12:21 ` Patrick Steinhardt
2026-02-05 15:50 ` Junio C Hamano [this message]
2026-02-06 6:31 ` Patrick Steinhardt
2026-02-06 16:25 ` Junio C Hamano
2026-02-06 16:58 ` Patrick Steinhardt
2026-02-06 16:25 ` [PATCH v2] " 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=xmqqms1nmbog.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=ps@pks.im \
/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.