From: "Torsten Bögershausen" <tboegi@web.de>
To: Josef Wolf <jw@raven.inka.de>, git@vger.kernel.org
Subject: Re: renormalize histroy with smudge/clean-filter
Date: Sun, 9 Feb 2025 12:14:06 +0100 [thread overview]
Message-ID: <20250209111406.GA12069@tb-raspi4> (raw)
In-Reply-To: <20250209092514.GM30202@raven.inka.de>
On Sun, Feb 09, 2025 at 10:25:14AM +0100, Josef Wolf wrote:
> On Sat, Feb 08, 2025 at 09:57:09PM +0100, Josef Wolf wrote:
>
> I just stumbled over another wirdeness:
>
> > Oh, have I mentioned that I am not only about line endings? Yes, I mentioned
> > it in the very first mail. In addition to line endings, I am also about XML
> > files from a proprietary application which reorders the XML-elements into a
> > random order every time it ist run. So the clean-filter needs to sort the
> > XML elements into some "canonical" order.
>
> This application stores the bulk of the data as text files and XML files with
> CRLF. But there are also some binary files. So I set gitattributes like this:
>
> # Catch bulk as text=crlf, rely on git to detect binary
> */* text=auto eol=crlf
This looks a little bit strange to me.
What happens if you replace "*/*" with "*" like this.
* text=auto eol=crlf
> #
> # those are known to be text=crlf
> */B text eol=crlf
> */P-* text eol=crlf
Same here. What is B ? Is it a directory ?
> #
> # smudge-clean filter
> */B filter=etsfile
> */P-* filter=etsfile
> #
> # files I dont't want to touch (mostly binaries)
> */*.dll -filter -text
> */*.ver -filter -text
> */*.lang -filter -text
> */*.store -filter -text
> */*.ets5hash -filter -text
*.dll -filter -text
(and the same for everything else)
>
> But "git ls-files --eol" gives me this:
>
> i/lf w/lf attr/text eol=crlf gt8/ETS/Projekte/P-0113/B
>
> Why is git ignoring my explicit CRLF setting?
>
> This is on linux and on Windows+MSYS2. I don't have $GIT_DIR/info/attributes
> and ~/.gitconfig also doesn't specify any line ending things
>
> --
> Josef Wolf
> jw@raven.inka.de
>
next prev parent reply other threads:[~2025-02-09 11:14 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 21:47 renormalize histroy with smudge/clean-filter Josef Wolf
2025-02-05 22:55 ` brian m. carlson
2025-02-05 23:59 ` Josef Wolf
2025-02-06 0:29 ` brian m. carlson
2025-02-06 8:07 ` Elijah Newren
2025-02-06 13:40 ` Josef Wolf
2025-02-06 20:04 ` Josef Wolf
2025-02-07 6:10 ` Chris Torek
2025-02-07 10:45 ` Josef Wolf
2025-02-07 11:06 ` Torsten Bögershausen
2025-02-07 11:12 ` Chris Torek
2025-02-07 11:17 ` Chris Torek
2025-02-07 14:01 ` Elijah Newren
2025-02-07 20:32 ` Josef Wolf
2025-02-08 0:23 ` Elijah Newren
2025-02-08 11:14 ` Phillip Wood
2025-02-08 21:08 ` Josef Wolf
2025-02-08 21:43 ` Elijah Newren
2025-02-08 23:26 ` Josef Wolf
2025-02-09 2:33 ` D. Ben Knoble
2025-02-09 8:53 ` Josef Wolf
2025-02-09 7:21 ` Elijah Newren
2025-02-09 8:57 ` Josef Wolf
2025-02-10 17:51 ` D. Ben Knoble
2025-02-08 20:57 ` Josef Wolf
2025-02-08 21:56 ` Elijah Newren
2025-02-09 9:25 ` Josef Wolf
2025-02-09 11:14 ` Torsten Bögershausen [this message]
2025-02-09 15:09 ` Josef Wolf
2025-02-09 17:54 ` Josef Wolf
2025-02-09 18:01 ` Josef Wolf
2025-02-07 20:21 ` Josef Wolf
2025-02-07 15:39 ` Junio C Hamano
2025-02-06 10:13 ` Phillip Wood
2025-02-06 7:55 ` Elijah Newren
2025-02-06 19:00 ` Junio C Hamano
2025-02-11 23:57 ` renormalize histroy with smudge/clean-filter, again Josef Wolf
2025-02-12 6:12 ` Torsten Bögershausen
2025-02-12 8:18 ` Josef Wolf
2025-02-13 11:36 ` Collisions while cloning (was: Re: renormalize histroy with smudge/clean-filter, again) Josef Wolf
2025-02-13 16:40 ` Torsten Bögershausen
2025-02-14 20:03 ` renormalize histroy with smudge/clean-filter, again Josef Wolf
2025-02-14 20:21 ` brian m. carlson
2025-02-14 20:55 ` Josef Wolf
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=20250209111406.GA12069@tb-raspi4 \
--to=tboegi@web.de \
--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).