git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Marius Storm-Olsen <marius@trolltech.com>
To: Steffen Prohaska <prohaska@zib.de>
Cc: Junio C Hamano <gitster@pobox.com>,
	Dmitry Kakurin <dmitry.kakurin@gmail.com>,
	Git Mailing List <git@vger.kernel.org>,
	Brian Downing <bdowning@lavos.net>
Subject: Re: [PATCH 2/2] checkout: fix attribute handling in checkout all
Date: Mon, 13 Aug 2007 09:15:33 +0200	[thread overview]
Message-ID: <46C00515.5050308@trolltech.com> (raw)
In-Reply-To: <5BA0164D-8327-4B01-84CD-595D8573BEEF@zib.de>

[-- Attachment #1: Type: text/plain, Size: 862 bytes --]

Steffen Prohaska said the following on 13.08.2007 08:50:
> On Aug 13, 2007, at 8:32 AM, Marius Storm-Olsen wrote:
>> In msysgit.git/etc/.gitattributes we have 'termcap -crlf', to avoid  
>> the termcaps being checked out with Windows EOL, if the user  
>> happens to have 'autocrlf = true'. However, when you checkout the  
>> working dir the first time it still has Windows EOL due to exactly  
>> this problem.
> 
> And exactly this is where I recognized the issue.
> 
> msysgit devs,
> We should really make autocrlf = true the default for us and fix
> all problems that we'll encounter. There may be more tricky stuff
> ahead, like merges, cherry-picks, ...

I'm more leaning towards having the installer give you the option to 
choose what kind of line-endings you want Git to work with; just like 
the Cygwin installer.

-- 
.marius


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 187 bytes --]

  reply	other threads:[~2007-08-13  7:14 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-12 20:34 [PATCH 1/2] attr: fix attribute handling if .gitattributes is involved Steffen Prohaska
2007-08-12 20:34 ` [PATCH 2/2] checkout: fix attribute handling in checkout all Steffen Prohaska
2007-08-12 21:50   ` Junio C Hamano
2007-08-12 22:26     ` Steffen Prohaska
2007-08-13  6:14     ` Junio C Hamano
2007-08-13  6:32       ` Marius Storm-Olsen
2007-08-13  6:50         ` Steffen Prohaska
2007-08-13  7:15           ` Marius Storm-Olsen [this message]
2007-08-13  7:32             ` Steffen Prohaska
2007-08-13  8:39               ` Marius Storm-Olsen
2007-08-13  8:51                 ` Steffen Prohaska
2007-08-13 14:35                   ` Dmitry Kakurin
2007-08-14  8:40         ` [PATCH 1/2] attr.c: refactoring Junio C Hamano
2007-08-14  8:41         ` [PATCH 2/2] attr.c: read .gitattributes from index as well Junio C Hamano
2007-08-13  6:46       ` [PATCH 2/2] checkout: fix attribute handling in checkout all Steffen Prohaska
2007-08-13 16:14         ` Johannes Schindelin
2007-08-13  7:24       ` David Kastrup
2007-08-13 14:55         ` git-update-ref bug? (was: [PATCH 2/2] checkout: fix attribute handling in checkout all) David Kastrup
2007-08-13 20:12         ` [PATCH 2/2] checkout: fix attribute handling in checkout all Junio C Hamano
2007-08-13  1:51 ` [PATCH 1/2] attr: fix attribute handling if .gitattributes is involved Brian Downing

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=46C00515.5050308@trolltech.com \
    --to=marius@trolltech.com \
    --cc=bdowning@lavos.net \
    --cc=dmitry.kakurin@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=prohaska@zib.de \
    /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).