From: David Aguilar <davvid@gmail.com>
To: Jens Bauer <jens-lists@gpio.dk>
Cc: git@vger.kernel.org
Subject: Re: CRLF, LF ... CR ?
Date: Thu, 13 Sep 2012 21:06:32 -0700 [thread overview]
Message-ID: <CAJDDKr5-ze2bhTkT+jzcS1iZipJO6kEr2qAf73GRn4QQ-rS1dQ@mail.gmail.com> (raw)
In-Reply-To: <20120913170943725232.01d717ef@gpio.dk>
On Thu, Sep 13, 2012 at 8:09 AM, Jens Bauer <jens-lists@gpio.dk> wrote:
> Hi everyone.
>
> I'm quite fond of git, and have used it for a while.
> Recently, I've started making printed circuit boards (PCBs) using an application called OsmondPCB (for Mac), and I'd like to use git to track changes on these.
> This application was originally written for the old Mac OS (Mac OS 6 to Mac OS 9.2).
> The old Mac OS does not use LF, nor CRLF for line endings, but only CR.
>
> I've read that git supports two different line endings; either CRLF or LF, but it does not support CR.
> Would it make sense to add support for CR (if so, I hereby request it as a new feature) ?
> The alternative is to ask the developer if he would change the file format, so that new versions of his software would change the files to end in LF, but he'd have to be careful not to break compatibility.
> If the software is to be changed, this would not fix similar issues that other people might have.
Do you mean that you want automatic conversion from CR to LF?
What's about just storing the files as-is,
with no conversion at all? (this is the default git behavior)
git doesn't really even support LF. It stores content as-is which
means LF works just fine. git prefers to not mess around with the content,
but we do have autocrlf to help folks stuck on windows.
If you need to, you can use .gitattributes to add a clean/smudge filter
that does this conversion for you.
See the "filter" section for an example:
http://www.kernel.org/pub/software/scm/git/docs/gitattributes.html
If you're serious about wanting that feature then we'll
happily review any patches you might have. That said, I don't really
think it's a common enough case for git to natively support, so
I'd recommend going with the .gitattributes filter.
good luck,
--
David
next prev parent reply other threads:[~2012-09-14 4:06 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-13 15:09 CRLF, LF ... CR ? Jens Bauer
2012-09-13 15:34 ` Drew Northup
2012-09-13 15:43 ` Jeff King
2012-09-13 15:53 ` Jens Bauer
2012-09-13 18:17 ` Jens Bauer
2012-09-13 18:23 ` Jeff King
2012-09-13 18:55 ` Jens Bauer
2012-09-13 18:34 ` Johannes Sixt
2012-09-13 19:13 ` Jens Bauer
2012-09-13 15:43 ` Erik Faye-Lund
2012-09-14 4:06 ` David Aguilar [this message]
2012-09-14 4:36 ` Jens Bauer
2012-09-14 4:51 ` Junio C Hamano
2012-09-26 8:42 ` David Aguilar
2012-09-26 10:12 ` Jens Bauer
2012-09-26 10:31 ` Jens Bauer
2012-09-27 6:16 ` Junio C Hamano
2012-09-27 13:42 ` Jens Bauer
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=CAJDDKr5-ze2bhTkT+jzcS1iZipJO6kEr2qAf73GRn4QQ-rS1dQ@mail.gmail.com \
--to=davvid@gmail.com \
--cc=git@vger.kernel.org \
--cc=jens-lists@gpio.dk \
/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).