From: Konstantin Khomoutov <flatworm@users.sourceforge.net>
To: Joshua Jensen <jjensen@workspacewhiz.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: What are the ways CRLF files can make it into the repository?
Date: Sat, 22 Sep 2012 16:08:21 +0400 [thread overview]
Message-ID: <20120922120821.GI32381@localhost.localdomain> (raw)
In-Reply-To: <505CB9B3.5010307@workspacewhiz.com>
On Fri, Sep 21, 2012 at 01:02:11PM -0600, Joshua Jensen wrote:
> We've been running with core.autocrlf = input (some people with
> core.autocrlf = true). However, there are some text files in the
> repository that are CRLF, and I am at a loss to explain how they go
> here.
>
> We understand that if core.autocrlf=false, this could happen. While
> I admit there is a remote possibility this did occur, I'm not
> convinced our people were smart enough with Git 1.5 years ago to
> make this configuration change.
>
> There are no .gitattributes settings for these source code files.
>
> Are there other ways CRLF files could sneak into the repository?
Is there any chance Git considered them binary for some reason and hence
did not apply its EOL-conversion logic at all?
prev parent reply other threads:[~2012-09-22 12:09 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-21 19:02 What are the ways CRLF files can make it into the repository? Joshua Jensen
2012-09-22 12:08 ` Konstantin Khomoutov [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=20120922120821.GI32381@localhost.localdomain \
--to=flatworm@users.sourceforge.net \
--cc=git@vger.kernel.org \
--cc=jjensen@workspacewhiz.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).