From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Sergio Callegari <sergio.callegari@gmail.com>, git@vger.kernel.org
Subject: Re: Interaction between clean/smudge and git status
Date: Mon, 14 Apr 2008 00:04:35 -0700 [thread overview]
Message-ID: <7vej98apdo.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <4802FE3C.4090306@viscovery.net> (Johannes Sixt's message of "Mon, 14 Apr 2008 08:48:28 +0200")
Johannes Sixt <j.sixt@viscovery.net> writes:
> Sergio Callegari schrieb:
>> I have tried for the first time the .gitattributes filter option, setting a
>> clean and a smudge filter for a certain type of files.
>>
>> What makes me wonder is that using filters, after a clean checkout git status
>> says that everything is changed.
What is to "re-zip"? You have a .zip file that contains a single file in
your work tree, and the index and the tree objects record that single file
deflated? When you "check out" from the index, you run smudge to create a
new .zip file with that single file?
>> Is this the expected behaviour of the smudge filter?
>
> I've observed this, too, and I don't think it is expected behavior. But it
> hasn't annoyed me enough to look at it in depth. Eventually I will, and I
> hope to find out what's wrong. ;)
Are you recreating the .zip file in the filter in such a way that a file
with the same contents results in byte-to-byte identical .zip file?
Otherwise as far as git is concerned you have changed the file in the work
tree.
next prev parent reply other threads:[~2008-04-14 7:05 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-13 23:25 Interaction between clean/smudge and git status Sergio Callegari
2008-04-14 6:48 ` Johannes Sixt
2008-04-14 7:04 ` Junio C Hamano [this message]
2008-04-14 7:21 ` Johannes Sixt
2008-04-14 7:38 ` Sergio Callegari
2008-04-14 8:18 ` Sergio Callegari
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=7vej98apdo.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=j.sixt@viscovery.net \
--cc=sergio.callegari@gmail.com \
/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).