From: "brian m. carlson" <sandals@crustytoothpaste.net>
To: Jonathon Anderson <janderson@acesquality.com>
Cc: Jeff King <peff@peff.net>,
"Randall S. Becker" <rsbecker@nexbridge.com>,
git@vger.kernel.org
Subject: Re: Git Modifying DLL
Date: Fri, 20 Aug 2021 19:14:40 +0000 [thread overview]
Message-ID: <YR//IDB9ml5RO2H6@camp.crustytoothpaste.net> (raw)
In-Reply-To: <CAG83euofNXHx8-=7Obj-Ju5U_fjwNBuLVJjmccVhe9bqRFyBiw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1795 bytes --]
On 2021-08-20 at 18:47:02, Jonathon Anderson wrote:
> On Fri, Aug 20, 2021 at 1:00 PM Jeff King <peff@peff.net> wrote:
> >
> > On Thu, Aug 19, 2021 at 01:21:03PM -0500, Jonathon Anderson wrote:
> >
> > > I had not. I tested that and it worked. I assumed that git would
> > > automatically treat dll files as binary. Thanks for the help!
> >
> > Git doesn't know about any file extensions by default. Its default "is
> > it binary" test looks for NUL bytes in the first 8k or so of the file.
> > I'd expect your DLL would probably have such a NUL byte.
> >
> > Is it possible you have other .gitattributes set which are confusing
> > things?
> >
> > You might try:
> >
> > git check-attr --all <path>
> >
> > or:
> >
> > git ls-files --stdin | git check-attr --stdin --all
> >
> > -Peff
>
> When I remove '*.dll binary" from .gitattributes, I get this:
>
> $ git check-attr --all ./PSWindowsUpdate.dll
> ./PSWindowsUpdate.dll: text: set
> ./PSWindowsUpdate.dll: eol: lf
Yes, this is definitely not correct. The flag "text" being set tells
Git to do line-ending conversion and "eol=lf" says to convert line
endings into LF.
You should look for things in your .gitattributes file that say
something like "* text", which you probably don't want. You could use
"* text=auto", which should be fine for most cases, though. It's also
possible those aren't in a .gitattributes file in your repository but
one elsewhere on your system. You can check gitattributes(5) for the
locations of other files that can affect it.
As a note, it is best practice not to check binary dependencies or build
artifacts into the repo. Those are best stored elsewhere, such as an
artifact server.
--
brian m. carlson (he/him or they/them)
Toronto, Ontario, CA
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 262 bytes --]
next prev parent reply other threads:[~2021-08-20 19:14 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-19 17:58 Git Modifying DLL Jonathon Anderson
2021-08-19 18:13 ` Randall S. Becker
2021-08-19 18:21 ` Jonathon Anderson
2021-08-20 15:37 ` Torsten Bögershausen
2021-08-20 18:00 ` Jeff King
2021-08-20 18:47 ` Jonathon Anderson
2021-08-20 19:14 ` brian m. carlson [this message]
2021-08-20 19:51 ` Randall S. Becker
2021-09-01 21:07 ` Jonathon Anderson
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=YR//IDB9ml5RO2H6@camp.crustytoothpaste.net \
--to=sandals@crustytoothpaste.net \
--cc=git@vger.kernel.org \
--cc=janderson@acesquality.com \
--cc=peff@peff.net \
--cc=rsbecker@nexbridge.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).