From: Junio C Hamano <gitster@pobox.com>
To: Josef Wolf <jw@raven.inka.de>
Cc: git@vger.kernel.org
Subject: Re: clean/smudge-filter with "attached file"?
Date: Wed, 26 Jan 2022 12:06:56 -0800 [thread overview]
Message-ID: <xmqqbkzyqn1b.fsf@gitster.g> (raw)
In-Reply-To: <20220126125209.GD16463@raven.inka.de> (Josef Wolf's message of "Wed, 26 Jan 2022 13:52:09 +0100")
Josef Wolf <jw@raven.inka.de> writes:
> Those files seemed to be good candidates for git's clean/smudge-filter.
Perhaps post-checkout hook to notice missing checksum files and
recompute them would work, but this is clearly outside of what
clean/smudge wants to do and what they were invented for (i.e. the
contents of the file in the working tree itself need to be adjusted
in the working tree and in the repository, hence there is a filter
in each direction). As the mechanism being "filter", i.e. a
bytestream is converted into another bytestream, it is not even
designed to muck with other things on the filesystem.
prev parent reply other threads:[~2022-01-26 20:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-26 12:52 clean/smudge-filter with "attached file"? Josef Wolf
2022-01-26 20:06 ` 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=xmqqbkzyqn1b.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jw@raven.inka.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 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).