-
Notifications
You must be signed in to change notification settings - Fork 74
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LF all the things #2378
LF all the things #2378
Conversation
Is this something that clang format wasn’t set up to do?
…On Sun, Apr 22, 2018 at 2:43 PM Benjamin Staneck ***@***.***> wrote:
the problem is since there never was a gitattributes file in the repo and
no editorconfig enforced, every windows commiter potenially changed some
files to CRLF, so this changes all crlf files back to lf.
not sure if best practice or not
------------------------------
You can view, comment on, or merge this pull request online at:
#2378
Commit Summary
- LF all the things
File Changes
- *M* .github/PULL_REQUEST_TEMPLATE.md
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-0> (10)
- *M* RELEASES <https://github.com/kvirc/KVIrc/pull/2378/files#diff-1>
(1084)
- *M* data/mimetypes/kvirc.xml
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-2> (38)
- *M* data/pics/Icon_license.txt
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-3> (24)
- *M* data/resources_win32/kvirc.rc
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-4> (116)
- *M* dist/debian/kvirc-data.links
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-5> (4)
- *M* dist/osx/osx_dmg.json
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-6> (18)
- *M* dist/windows/CMakeLists.txt
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-7> (14)
- *M* dist/windows/translations/CMakeLists.txt
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-8> (12)
- *M* dist/windows/translations/belarusian.nsi
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-9> (0)
- *M* dist/windows/translations/french.nsi
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-10> (0)
- *M* dist/windows/translations/german.nsi
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-11> (0)
- *M* dist/windows/translations/italian.nsi
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-12> (0)
- *M* dist/windows/translations/japanese.nsi
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-13> (0)
- *M* dist/windows/translations/russian.nsi
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-14> (0)
- *M* dist/windows/translations/spanish.nsi
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-15> (0)
- *M* dist/windows/translations/ukrainian.nsi
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-16> (0)
- *M* doc/ABOUT-LICENSE
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-17> (126)
- *M* src/modules/tip/libkvitip_fi.kvc
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-18> (52)
- *M* src/modules/tip/libkvitip_uk.kvc
<https://github.com/kvirc/KVIrc/pull/2378/files#diff-19> (52)
Patch Links:
- https://github.com/kvirc/KVIrc/pull/2378.patch
- https://github.com/kvirc/KVIrc/pull/2378.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<#2378>, or mute the thread
<https://github.com/notifications/unsubscribe-auth/AF95SyIrXdtmogMnWyKDumggoD6_wU1Tks5trPmIgaJpZM4TfCna>
.
|
that is actually something you can't even tell clang-format to do. At least I haven't been able to find out how. |
Well, if this means that the repo is consistently LF then +1 here
…On Sun, Apr 22, 2018 at 2:45 PM Benjamin Staneck ***@***.***> wrote:
that is actually something you can't even tell clang-format to do. At
least I haven't been able to find out how.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#2378 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AF95S0M9WSOq6XXvdwlDIuBk6YKhpd43ks5trPoQgaJpZM4TfCna>
.
|
I am no expert on .gitgnore but it is currently set up like this:
is this enough? |
What about utf-8 all the things too? It might be a good opportunity to do that as well if we want that. We have an assortment of binary, us-ascii, and utf-8 charsets for our .cpp and .h files. |
How is that possible? Remember that |
Note that ASCII is a subset of UTF-8 |
^ A file that doesn't contain accents or weird stuff could pass as a us-ascii file |
Can we settle the LF thing first, please? :D My .gitattributes does not cover all files we have in the repo, do we need more? Something like https://github.com/alexkaratarakis/gitattributes |
reference cross-platform project |
@craftwar that is what I thought before, then someone told me otherwise: vercel/hyper#2795 not sure if true or not. What yours will do is let your local Git installation decide on what to do, based on the core.autoCRLF setting, afaik. |
@Stanzilla according to git document https://git-scm.com/docs/gitattributes add |
nsi are binary files because they are not written in utf-8. Don't convert them to utf-8!!! |
So what we should do is tell Git which files are binary so it ignores it, like that https://github.com/alexkaratarakis/gitattributes/blob/master/C%2B%2B.gitattributes |
These should be tested. I am not sure if nsis works with utf-8 now, that's why I insisted on not converting them |
sure, just waiting for appveyor |
This UTF-8 stuff probably should have been left to another PR since this PR was intended to be specific towards line endings. Now it seems like we're dealing with 2 unrelated issues. |
Yeah agree, but it's done now, I could still split it off if wanted |
Eh, it's fine. Moving forward, let's just keep PRs specific towards the topic. Otherwise things will get backlogged due to unrelated debates. |
Build is green, any last words? |
the problem is since there never was a gitattributes file in the repo and no editorconfig enforced, every windows commiter potenially changed some files to CRLF, so this changes all crlf files back to lf.
not sure if best practice or not