git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rusi Mody <rustompmody@gmail.com>
To: msysgit@googlegroups.com
Cc: git@vger.kernel.org, rustompmody@gmail.com
Subject: Re: crlf issues
Date: Fri, 19 Jun 2015 08:29:18 -0700 (PDT)	[thread overview]
Message-ID: <06bed56e-b934-43e1-af1e-df1253c07dac@googlegroups.com> (raw)
In-Reply-To: <b1d861878d2f0a4414490439bf865cbb@www.dscho.org>


[-- Attachment #1.1: Type: text/plain, Size: 2869 bytes --]



On Friday, June 19, 2015 at 7:41:00 PM UTC+5:30, Johannes Schindelin wrote:
>
> Hi Rusi, 
>
> Cc:ing the main Git list, as some of this has been discussed at the 
> GitMerge in Paris, and some participants of that discussion might want to 
> join this thread. 
>   
> On 2015-06-19 14:55, Rusi Mody wrote: 
> > Trying to setup git. 
> > Majority folks are MS VS users but also some *nixers. 
> > 
> > My current understanding/analysis of the situation: 
> > 
> > 1. autocrlf is broken -- keep it false 
> > 2. safecrlf is a cure (to some extent) -- keep it true 
> > 3. core.eol can be left native (or is crlf on windows/lf on *nix 
> > preferred??) 
> > 
> > And of course most crucial: 
> > 4. Make sure ALL file types are covered in .gitattributes; eg 
> > 
> > *.txt text 
> > *.cs text 
> > : 
> > : 
> > *.pdf binary 
> > etc 
> > 
> > Still when we get a merge conflict the file (created by git with 
> conflict 
> > markers) shows ^M in vi 
> > ie I assume its unclean line endings. 
> > 
> > Any tips what to do? 
>
> The most important preliminary question is: how cross platform is your 
> project?


Somewhat complex question...
Almost completely windows as of now.
Good chance of starting to migrate to Linux shortly... little by little and 
would like to minimize future headches.
 

> If there is no risk of any developer working on a non-Windows platform, 
> you could simply commit CRLF and be done with it. 
>

Ok. So what are the (set of) settings for that?
- MS-only project
- No conversions any which way
seems to be a better starting compromise than broken to start with :-)


As to autocrlf: I actually had some good experience with setting it to 
> `input` when working with other developers. 
>


Can hardly claim to be expert on this but general impression I got from 
searching the net is autocrlf is more broken than working
and so best avoided
eg
http://stackoverflow.com/questions/2333424/distributing-git-configuration-with-the-code/2354278#2354278 

-- 
-- 
*** Please reply-to-all at all times ***
*** (do not pretend to know who is subscribed and who is not) ***
*** Please avoid top-posting. ***
The msysGit Wiki is here: https://github.com/msysgit/msysgit/wiki - Github accounts are free.

You received this message because you are subscribed to the Google
Groups "msysGit" group.
To post to this group, send email to msysgit@googlegroups.com
To unsubscribe from this group, send email to
msysgit+unsubscribe@googlegroups.com
For more options, and view previous threads, visit this group at
http://groups.google.com/group/msysgit?hl=en_US?hl=en

--- 
You received this message because you are subscribed to the Google Groups "Git for Windows" group.
To unsubscribe from this group and stop receiving emails from it, send an email to msysgit+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 3882 bytes --]

  reply	other threads:[~2015-06-19 15:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <f96f4550-af8c-48b9-98ef-2c1f3282d8a7@googlegroups.com>
2015-06-19 14:10 ` [msysGit] crlf issues Johannes Schindelin
2015-06-19 15:29   ` Rusi Mody [this message]
2015-06-20  6:21     ` Rusi Mody

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=06bed56e-b934-43e1-af1e-df1253c07dac@googlegroups.com \
    --to=rustompmody@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=msysgit@googlegroups.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).