From: Johannes Sixt <j6t@kdbg.org>
To: Andreas Leha <andreas.leha@med.uni-goettingen.de>
Cc: git@vger.kernel.org
Subject: Re: make git ignore the timestamp embedded in PDFs
Date: Sat, 18 May 2013 18:32:58 +0200 [thread overview]
Message-ID: <5197AD3A.5050500@kdbg.org> (raw)
In-Reply-To: <87ppwohgyd.fsf@med.uni-goettingen.de>
Am 18.05.2013 09:42, schrieb Andreas Leha:
>> Am 14.05.2013 15:17, schrieb Andreas Leha:
>>> Hi all,
>>>
>>> how can I make git ignore the time stamp(s) in a PDF. Two PDFs that
>>> differ only in these time stamps should be considered identical.
>>> ...
>>> What I tried is a filter:
>>> ,----[ ~/.gitconfig ]
>>> | [filter "pdfresetdate"]
>>> | clean = pdfresetdate
>>> `----
>>>
>>> This 'works' as far as the committed pdf indeed has the date reset to my
>>> default value.
>>>
>>> However, when I re-checkout the files, they are marked modified by git.
>>
>> I'm using cleaned files every now and then, but not on Linux. I have
>> never observed this behavior recently.
>>
>> If you 'git add' the file, does it keep its modified state? Does 'git
>
> yes.
>
>> diff' tell a difference?
>
> no.
I do not believe you. I'm sure that "Binary files differ" was reported.
The reason is that your pdfresetdate script is not idempotent. Look:
$ pdfresetdate < x.pdf > y.pdf
$ pdfresetdate < y.pdf > z.pdf
$ md5sum x.pdf y.pdf z.pdf
c46a7097574a035e89d1a46d93c83528 x.pdf
8e6d942b4cc7d8a4dfe6898867573617 y.pdf
e6333bc0f8ab9781d3e1d811a392d516 z.pdf
A file that was already cleaned by the clean filter must not be
modified, i.e., the y.pdf and z.pdf should be identical. But they are not.
Fix your clean filter.
-- Hannes
next prev parent reply other threads:[~2013-05-18 16:33 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-05-14 13:17 make git ignore the timestamp embedded in PDFs Andreas Leha
2013-05-14 19:26 ` Johannes Sixt
2013-05-18 7:42 ` Andreas Leha
2013-05-18 16:32 ` Johannes Sixt [this message]
2013-05-18 18:09 ` Andreas Leha
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=5197AD3A.5050500@kdbg.org \
--to=j6t@kdbg.org \
--cc=andreas.leha@med.uni-goettingen.de \
--cc=git@vger.kernel.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.
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).