git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ryan McCue <me@ryanmccue.info>
To: git@vger.kernel.org
Subject: Forcing CRLF for files in a directory
Date: Thu, 01 Jul 2010 22:12:52 +1000	[thread overview]
Message-ID: <4C2C8644.4060208@ryanmccue.info> (raw)

Hi there,

I'm working on a project at the moment which stores raw HTTP header data 
along with bodies for use during testing. As each header line must be 
separated by a CRLF, these need to remain so in the repository.

My question is: Do I need to do anything special to ensure these CRLFs 
aren't converted to LFs during checkout?

Thanks,
Ryan.

             reply	other threads:[~2010-07-01 12:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-07-01 12:12 Ryan McCue [this message]
2010-07-01 13:37 ` Forcing CRLF for files in a directory Eyvind Bernhardsen
2010-07-01 13:55 ` Finn Arne Gangstad

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=4C2C8644.4060208@ryanmccue.info \
    --to=me@ryanmccue.info \
    --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).