From: Ramkumar Ramachandra <artagnon@gmail.com>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: git@vger.kernel.org, timar74@gmail.com
Subject: Re: gitattributes - clean filter invoked on pull?
Date: Mon, 11 Apr 2011 14:49:21 +0530 [thread overview]
Message-ID: <20110411091919.GE28959@kytes> (raw)
In-Reply-To: <20110411084229.GW5146@genesis.frugalware.org>
Hi Miklos,
Miklos Vajna writes:
> Background: We at LibreOffice are trying to use the 'filter'
> gitattributes feature to clean up line wrappings in po files.
>
> The problem is that it seems the clean filter - which is supposed to be
> invoked only in case a new blob is created - is invoked even on
> clone/pull, and other developers are claiming that it slows down their
> workflow.
>
> Is this a bug? I don't exactly understand why this would be necessary.
>From config.txt:
- 'clean' is "The command which is used to convert the content of a
worktree file to a blob upon checkin".
- 'smudge' is "The command which is used to convert the content of a
blob object to a worktree file upon checkout."
According to the documentation, 'smudge' is *supposed* to be invoked
on a clone/ pull, since it involves a checkout. I don't see how you
can avoid running these filters on every checkin/ checkout unless you
cache the result somewhere.
-- Ram
next prev parent reply other threads:[~2011-04-11 9:20 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 8:42 gitattributes - clean filter invoked on pull? Miklos Vajna
2011-04-11 9:19 ` Ramkumar Ramachandra [this message]
2011-04-11 9:31 ` Miklos Vajna
2011-04-11 9:50 ` Ramkumar Ramachandra
2011-04-11 10:00 ` Johannes Sixt
2011-04-11 9:50 ` Michael J Gruber
2011-04-11 10:16 ` Miklos Vajna
2011-04-11 10:41 ` Michael J Gruber
2011-04-11 11:14 ` Miklos Vajna
2011-04-11 10:04 ` Dmitry Potapov
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=20110411091919.GE28959@kytes \
--to=artagnon@gmail.com \
--cc=git@vger.kernel.org \
--cc=timar74@gmail.com \
--cc=vmiklos@frugalware.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).