Johannes Schindelin wrote Tuesday, May 26, 2009 2:10 PM
Hi,
On Tue, 26 May 2009, Carl D. Sorensen wrote:
When I make my own patches, they're Unix line endings.
Trevor, could you do a quick search for the fixes you've pushed,
and
identify the patches that caused the problem?
You can let Git search for you:
$ git log -S"$(printf "\r")"
If you want to see the corresponding patches, too, say
$ git log -S"$(printf "\r")" -p
Neither of these git commands produced any output
in my local (Windows) repo, but the latest 5 fixes
for Mac line endings which I have pushed are:
7643225b3deedaed6198a89fde011efec1a2f47c 2009-04-06
e655daf816a1cfa8a41a535a34eed106cef49ec9 2008-12-09
4df51915f96d56a76345d35c98b7795a01bd6540 2008-11-30
b314856c905ac499d115564e6db6d52ba3b92026 2008-11-19
0c582192866e9f07d45513a8431fbe2c38fac9b7 2008-11-17
The corresponding commits which produced the Mac
endings were (I think):
3684489ec07c20677c11cf047db95ee7b4857c78
3de153c685a890d8b56aa4ec9edfc7600ceacd6e
f22ee8a434f0c884ea2ce6bbb8d5b3a3167c2f0b (plus others?)
3acc3f7df6492e6334619ae708bee13180028a4d
afcbe5d595f910a5ebe6040f201957d0361ff8fd
(Sorry for the delayed reply - I had a family
bereavement to attend to recently)
Trevor
_______________________________________________
lilypond-devel mailing list
lilypond-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-devel