From: "Torsten Bögershausen" <tboegi@web.de>
To: Francis ANDRE <francis.andre.kampbell@orange.fr>, git@vger.kernel.org
Subject: Re: Git improvement for line feed processing: LF versus CR-LF
Date: Mon, 08 Sep 2014 11:29:41 +0200 [thread overview]
Message-ID: <540D7705.4000405@web.de> (raw)
In-Reply-To: <540D6EEB.2040101@orange.fr>
On 09/08/2014 10:55 AM, Francis ANDRE wrote:
> Hi
> []
> All text file line endings in the repository must be Unix-style (LF).
> This includes Visual Studio project and solution files (.sln, .vcproj,
> .vcxproj, .vcxproj.filters).
>
> But git-gui translates states:
> warning: LF will be replaced by CRLF in file.txt. The file will have
> its original line endings in your working directory.
>
> Could you add a option to git-gui to specify to translate or not the
> end of line of the cloned repository so that my fixes be accepted by
> the owner of the repository.
>
> Thanks
Unless I'm completely wrong, such an option already exists, please see
http://git-htmldocs.googlecode.com/git/gitattributes.html
prev parent reply other threads:[~2014-09-08 9:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-08 8:55 Git improvement for line feed processing: LF versus CR-LF Francis ANDRE
2014-09-08 9:29 ` Torsten Bögershausen [this message]
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=540D7705.4000405@web.de \
--to=tboegi@web.de \
--cc=francis.andre.kampbell@orange.fr \
--cc=git@vger.kernel.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).