git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Miklos Vajna <vmiklos@frugalware.org>
Cc: Ramkumar Ramachandra <artagnon@gmail.com>,
	git@vger.kernel.org, timar74@gmail.com
Subject: Re: gitattributes - clean filter invoked on pull?
Date: Mon, 11 Apr 2011 12:41:10 +0200	[thread overview]
Message-ID: <4DA2DAC6.1010009@drmicha.warpmail.net> (raw)
In-Reply-To: <20110411101614.GB5146@genesis.frugalware.org>

Miklos Vajna venit, vidit, dixit 11.04.2011 12:16:
> On Mon, Apr 11, 2011 at 11:50:09AM +0200, Michael J Gruber <git@drmicha.warpmail.net> wrote:
>> But maybe there is a better solution for your actual use case? Do you
>> want to ignore line wrap or normalise it?
> 
> I want to avoid those, so we get readable diffs, whatever line width the
> different translator tools are using. (If tool1 is using 72 and tool2 is
> using 80, then it would reformat the whole file.)
> 
> Do you have a better idea than
> 
>         git config filter.po.clean 'msgcat - --no-wrap'
> 
> ?

git config diff.po.textconv 'msgcat - --no-wrap'
git config diff.po.cachetextconv true

If you want to normalise the repo, you may want to look at hooks instead
of clean/smudge if they are a performance problem.

Michael

  reply	other threads:[~2011-04-11 10:41 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
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 [this message]
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=4DA2DAC6.1010009@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=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).