David Aguilar dav...@gmail.com writes:
That said, perhaps the autocrlf code is simple enough that it
could be easily tweaked to also handle this special case,...
I wouldn't be surprised if it is quite simple.
We (actually Linus, IIRC) simply declared from the get-go that it is
not worth
Hi Junio and David.
Rule is in fact quite simple.
If it's a text-file and it contains a LF, a CRLF or a CR, then that's a
line-break. :)
-So everywhere a LF is checked for, a CR should most likely be checked for.
Usually, when checking for CRLF, one is looking for the LF. If a CR precedes
the
On Thu, Sep 13, 2012 at 9:51 PM, Junio C Hamano gits...@pobox.com wrote:
David Aguilar dav...@gmail.com writes:
git doesn't really even support LF.
At the storage level that is correct, but the above is a bit of
stretch. It may not be support, but git _does_ rely on LF when
running many
Hi David and Junio.
At first, I was planning to reply that I'd probably not be qualified for that.
But to tell the truth, I have been writing a lot of CR/LF/CRLF code throughout
the years, so maybe I could do it.
Unfortunately, I have to go slow about programming, because I burned myself out
a
Hi David and Junio.
Woops, that's what happens when deleting a block of lines in a message...
The CR/LF/CRLF implementation depends a lot on if git is reading a stream or
reading from memory.
I'd like to correct the last line to read...
Worst case is, if a file contains mixed CR, LF and CRLF,
Hi Jeff and Drew.
I've been messing a little with clean/smudge filters; I think I understand them
partly.
Let's call the file I have on the server that have cr line endings,
mypcb.osm.
If I clone the project, and do the following...
$ cat mypcb.osm | tr '\r' '\n'
I can read the file in the
On Thu, Sep 13, 2012 at 08:17:20PM +0200, Jens Bauer wrote:
In my home directory, I have a .gitconfig file, here's the interesting part:
[core]
editor = nano
excludesfile = /Users/jens/.gitexcludes
attributesfile = /Users/jens/.gitattributes
[filter cr]
Hi Jeff and Drew.
Excellent. I now removed the repository from the server, removed it from my
gitolite.conf, added it to gitolite.conf, re-initialized and it works.
git diff shows what I wanted.
Thank you *very* much for making my dream come true. :)
-And thank you all for all the hard work
Hi Johannes.
I've changed...
tr '\\r' '\\n'
...to...
tr '\\15' '\\12'
...As you are right in that it is more correct. (Then in theory, it would be
portable).
[I once came across tftpd, tried compiling it on a Mac, but it failed to work,
because \r and \n were swapped on the
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
David Aguilar dav...@gmail.com writes:
git doesn't really even support LF.
At the storage level that is correct, but the above is a bit of
stretch. It may not be support, but git _does_ rely on LF when
running many text oriented operations (a rough rule of thumb is
does 'a line' in a file
11 matches
Mail list logo
