On Thu, Sep 13, 2012 at 8:09 AM, Jens Bauer <jens-li...@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:


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,
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to