Set line endings on a specific file within my local repository





.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}







0















We have a file in our repository that has crlf line endigs. However in my local environment I would like to have lf line endigs in that file. Is there a way to do that?



I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository. Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.






git







share|improve this question





























    0















    We have a file in our repository that has crlf line endigs. However in my local environment I would like to have lf line endigs in that file. Is there a way to do that?



    I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository. Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.






    git







    share|improve this question

























      0












      0








      0








      We have a file in our repository that has crlf line endigs. However in my local environment I would like to have lf line endigs in that file. Is there a way to do that?



      I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository. Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.






      git







      share|improve this question














      We have a file in our repository that has crlf line endigs. However in my local environment I would like to have lf line endigs in that file. Is there a way to do that?



      I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository. Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.






      git




      git






      share|improve this question













      share|improve this question











      share|improve this question




      share|improve this question










      asked Nov 22 '18 at 14:15









      BehnilBehnil

      1,56121744




      1,56121744
























          1 Answer
          1






          active

          oldest

          votes


















          0















          I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository.




          I don't know what you mean. Yes, attributes (in particular the text and eol attributes) can be used to set line endings for a file; that's not a matter of opinion.




          Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.




          Attributes that should not be checked in are placed in .git/info/attributes (just as ignore rules that should not be checked in are placed in .git/info/excludes)






          share|improve this answer
























          • I did put attributes file in .git/info folder with content set to task text eol=lf where task is name of the file I would like to use with lf line endings, but when I try change line endings in the task file to lf and run git status it still tells me the file task is modified.

            – Behnil
            Nov 22 '18 at 15:36






          • 1





            @Behnil: Changes in the worktree are detected by comparing stat info. If you manually change the line endings, the stat info won't match, and the file will appear to have changed. I would expect if you git add the file, ti will no longer be shown as changed (and will also not show up as a staged change); but I'd say the "right" way to handle it is to delete and re-checkout the file (as the checkout is when line ending filters are applied).

            – Mark Adelsberger
            Nov 22 '18 at 15:44














          Your Answer






          StackExchange.ifUsing("editor", function () {
          StackExchange.using("externalEditor", function () {
          StackExchange.using("snippets", function () {
          StackExchange.snippets.init();
          });
          });
          }, "code-snippets");

          StackExchange.ready(function() {
          var channelOptions = {
          tags: "".split(" "),
          id: "1"
          };
          initTagRenderer("".split(" "), "".split(" "), channelOptions);

          StackExchange.using("externalEditor", function() {
          // Have to fire editor after snippets, if snippets enabled
          if (StackExchange.settings.snippets.snippetsEnabled) {
          StackExchange.using("snippets", function() {
          createEditor();
          });
          }
          else {
          createEditor();
          }
          });

          function createEditor() {
          StackExchange.prepareEditor({
          heartbeatType: 'answer',
          autoActivateHeartbeat: false,
          convertImagesToLinks: true,
          noModals: true,
          showLowRepImageUploadWarning: true,
          reputationToPostImages: 10,
          bindNavPrevention: true,
          postfix: "",
          imageUploader: {
          brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
          contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
          allowUrls: true
          },
          onDemand: true,
          discardSelector: ".discard-answer"
          ,immediatelyShowMarkdownHelp:true
          });


          }
          });














          draft saved

          draft discarded


















          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432891%2fset-line-endings-on-a-specific-file-within-my-local-repository%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown

























          1 Answer
          1






          active

          oldest

          votes








          1 Answer
          1






          active

          oldest

          votes









          active

          oldest

          votes






          active

          oldest

          votes









          0















          I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository.




          I don't know what you mean. Yes, attributes (in particular the text and eol attributes) can be used to set line endings for a file; that's not a matter of opinion.




          Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.




          Attributes that should not be checked in are placed in .git/info/attributes (just as ignore rules that should not be checked in are placed in .git/info/excludes)






          share|improve this answer
























          • I did put attributes file in .git/info folder with content set to task text eol=lf where task is name of the file I would like to use with lf line endings, but when I try change line endings in the task file to lf and run git status it still tells me the file task is modified.

            – Behnil
            Nov 22 '18 at 15:36






          • 1





            @Behnil: Changes in the worktree are detected by comparing stat info. If you manually change the line endings, the stat info won't match, and the file will appear to have changed. I would expect if you git add the file, ti will no longer be shown as changed (and will also not show up as a staged change); but I'd say the "right" way to handle it is to delete and re-checkout the file (as the checkout is when line ending filters are applied).

            – Mark Adelsberger
            Nov 22 '18 at 15:44


















          0















          I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository.




          I don't know what you mean. Yes, attributes (in particular the text and eol attributes) can be used to set line endings for a file; that's not a matter of opinion.




          Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.




          Attributes that should not be checked in are placed in .git/info/attributes (just as ignore rules that should not be checked in are placed in .git/info/excludes)






          share|improve this answer
























          • I did put attributes file in .git/info folder with content set to task text eol=lf where task is name of the file I would like to use with lf line endings, but when I try change line endings in the task file to lf and run git status it still tells me the file task is modified.

            – Behnil
            Nov 22 '18 at 15:36






          • 1





            @Behnil: Changes in the worktree are detected by comparing stat info. If you manually change the line endings, the stat info won't match, and the file will appear to have changed. I would expect if you git add the file, ti will no longer be shown as changed (and will also not show up as a staged change); but I'd say the "right" way to handle it is to delete and re-checkout the file (as the checkout is when line ending filters are applied).

            – Mark Adelsberger
            Nov 22 '18 at 15:44
















          0












          0








          0








          I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository.




          I don't know what you mean. Yes, attributes (in particular the text and eol attributes) can be used to set line endings for a file; that's not a matter of opinion.




          Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.




          Attributes that should not be checked in are placed in .git/info/attributes (just as ignore rules that should not be checked in are placed in .git/info/excludes)






          share|improve this answer














          I found some information about configuration file .gitattributes but using this configuration file IMHO I can set line endings for a particular files within the repository.




          I don't know what you mean. Yes, attributes (in particular the text and eol attributes) can be used to set line endings for a file; that's not a matter of opinion.




          Moreover this file should be commited to the repository and therefore used by all users. I don't want to force other users to checkout this file with lf line endings.




          Attributes that should not be checked in are placed in .git/info/attributes (just as ignore rules that should not be checked in are placed in .git/info/excludes)







          share|improve this answer












          share|improve this answer



          share|improve this answer










          answered Nov 22 '18 at 14:25









          Mark AdelsbergerMark Adelsberger

          22.2k11322




          22.2k11322













          • I did put attributes file in .git/info folder with content set to task text eol=lf where task is name of the file I would like to use with lf line endings, but when I try change line endings in the task file to lf and run git status it still tells me the file task is modified.

            – Behnil
            Nov 22 '18 at 15:36






          • 1





            @Behnil: Changes in the worktree are detected by comparing stat info. If you manually change the line endings, the stat info won't match, and the file will appear to have changed. I would expect if you git add the file, ti will no longer be shown as changed (and will also not show up as a staged change); but I'd say the "right" way to handle it is to delete and re-checkout the file (as the checkout is when line ending filters are applied).

            – Mark Adelsberger
            Nov 22 '18 at 15:44





















          • I did put attributes file in .git/info folder with content set to task text eol=lf where task is name of the file I would like to use with lf line endings, but when I try change line endings in the task file to lf and run git status it still tells me the file task is modified.

            – Behnil
            Nov 22 '18 at 15:36






          • 1





            @Behnil: Changes in the worktree are detected by comparing stat info. If you manually change the line endings, the stat info won't match, and the file will appear to have changed. I would expect if you git add the file, ti will no longer be shown as changed (and will also not show up as a staged change); but I'd say the "right" way to handle it is to delete and re-checkout the file (as the checkout is when line ending filters are applied).

            – Mark Adelsberger
            Nov 22 '18 at 15:44



















          I did put attributes file in .git/info folder with content set to task text eol=lf where task is name of the file I would like to use with lf line endings, but when I try change line endings in the task file to lf and run git status it still tells me the file task is modified.

          – Behnil
          Nov 22 '18 at 15:36





          I did put attributes file in .git/info folder with content set to task text eol=lf where task is name of the file I would like to use with lf line endings, but when I try change line endings in the task file to lf and run git status it still tells me the file task is modified.

          – Behnil
          Nov 22 '18 at 15:36




          1




          1





          @Behnil: Changes in the worktree are detected by comparing stat info. If you manually change the line endings, the stat info won't match, and the file will appear to have changed. I would expect if you git add the file, ti will no longer be shown as changed (and will also not show up as a staged change); but I'd say the "right" way to handle it is to delete and re-checkout the file (as the checkout is when line ending filters are applied).

          – Mark Adelsberger
          Nov 22 '18 at 15:44







          @Behnil: Changes in the worktree are detected by comparing stat info. If you manually change the line endings, the stat info won't match, and the file will appear to have changed. I would expect if you git add the file, ti will no longer be shown as changed (and will also not show up as a staged change); but I'd say the "right" way to handle it is to delete and re-checkout the file (as the checkout is when line ending filters are applied).

          – Mark Adelsberger
          Nov 22 '18 at 15:44






















          draft saved

          draft discarded




















































          Thanks for contributing an answer to Stack Overflow!


          • Please be sure to answer the question. Provide details and share your research!

          But avoid …



          • Asking for help, clarification, or responding to other answers.

          • Making statements based on opinion; back them up with references or personal experience.


          To learn more, see our tips on writing great answers.




          draft saved


          draft discarded














          StackExchange.ready(
          function () {
          StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53432891%2fset-line-endings-on-a-specific-file-within-my-local-repository%23new-answer', 'question_page');
          }
          );

          Post as a guest















          Required, but never shown





















































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown

































          Required, but never shown














          Required, but never shown












          Required, but never shown







          Required, but never shown







          -

          Popular posts from this blog

          Guess what letter conforming each word

          Image
          6 $begingroup$ This is an entry in the Fortnightly Topic Challenge #41: Short and Sweet. 1 letter only could be mean anything . With an additional letter in front , could be used as medicine component and something you definitely learn or at least heard once. Add another letter in front , you would possibly hear that many times . Add an additional letter in front , you would found an independent country . With an additional letter, in the end , you would found something related to apple . Add another letter in the end , you would found something bad . Hint: Each letter is unique . word knowledge letters chemistry share | improve this question ...
          Read more

          Port of Spain

          Image
          For ports in the country of Spain, see List of ports in Spain. City in City of Port of Spain, Trinidad and Tobago Port of Spain City City of Port of Spain Top to bottom (left to right): Skyline of Port of Spain from Gulf of Paria; National Academy for the Performing Arts, Independence Square, Eric Williams Plaza; MovieTowne, Port of Port of Spain Motto(s):  "We Gather Strength As We Go Along" Port of Spain Coordinates: 10°40′N 61°31′W  /  10.667°N 61.517°W  / 10.667; -61.517 Coordinates: 10°40′N 61°31′W  /  10.667°N 61.517°W  / 10.667; -61.517 Country   Trinidad and Tobago Jurisdiction City of Port of Spain Settled 1560 Incorporated (town) 1853 Incorporated (city) 1914 Government  • Mayor Joel Martinez  • Governing body City Corporation Area [1]  • City 12 km 2 (5 sq mi) Elevation [2] 66 m (217 ft) Population (2011) [1]  • City 37,074  • Rank 3rd  • Density 3,090/km 2 (8,000/sq mi)...
          Read more

          Run scheduled task as local user group (not BUILTIN)

          Image
          0 I am trying to run a scheduled task with User Group (not a single user). This is working fine when I in the field "when running a task, use the following user account:" insert BUILTIN User Group (for example: Administrators or Users). But when I try it with the created Local User Group (example: TestGroup) it is not working. The Users in the TestGroup are the same as in the Administrators group. What could be the problem? Are there some restrictions to the Created User Group compared to BUILTINUsers? scheduled-tasks taskscheduler windowstaskschedule share | improve this question asked Nov 15 '18 at 15:36 Far...
          Read more