From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Joey Hess <id@joeyh.name>, git@vger.kernel.org
Subject: Re: buggy smudge/clean of empty files
Date: Thu, 22 May 2025 15:26:42 -0700 [thread overview]
Message-ID: <xmqqr00g2sf1.fsf@gitster.g> (raw)
In-Reply-To: <20250522221523.GA21347@coredump.intra.peff.net> (Jeff King's message of "Thu, 22 May 2025 18:15:23 -0400")
Jeff King <peff@peff.net> writes:
> So I dunno. I'm hoping somebody more familiar with the index and/or
> clean/smudge conversions can show a better way.
My initial reaction was "well, do not do it then---an emptyness
smudges to and cleans to an emptyness and that is either by design,
or is a known limitation of the design of smudge/clean".
If somebody can show a clean way to lift that assumption buried deep
inside the design, that would indeed be nice ;-)
Thanks.
prev parent reply other threads:[~2025-05-22 22:26 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-22 19:01 buggy smudge/clean of empty files Joey Hess
2025-05-22 22:15 ` Jeff King
2025-05-22 22:26 ` Junio C Hamano [this message]
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=xmqqr00g2sf1.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=id@joeyh.name \
--cc=peff@peff.net \
/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).