"Leslie P. Polzer"
writes:
> FWIW I guess most projects wouldn't accept such a patch. It's
I understand that perfectly, which is why I was happy to provide
a new patch. No harm done. It's just that I've forced everone
on my team for 10 years to use the same .emacs file, so there's
never any "e
Alain Picard wrote:
> That's because my emacs automatically cleans up the whitespace
> as a file saving hook --- something I would heartily recommend
> to any developer using emacs. But since this isn't my project,
> I will again try to make a simpler patch.
FWIW I guess most projects wouldn't
Alain Picard
writes:
OK - here is a MINIMAL patch. It applies with
patch -p1 < /tmp/patch.
Hope this one works!
--ap
diff -rN -wu old-elephant-1.0-work/src/elephant/controller.lisp new-elephant-1.0-work/src/elephant/controller.lisp
--- old-elephant-1.0-work/src/elephant/controller.lisp 20
"Leslie P. Polzer"
writes:
> Alain Picard wrote:
>
>>> You could also make a Darcs patch using "darcs record" followed by
>>> "darcs send -o mypatch", although in the general case I prefer plain
>>> diffs.
>>
>> OK - here's a patch produced as above.
>
> Thank you, this one applies.
>
> But the p
Alain Picard wrote:
>> You could also make a Darcs patch using "darcs record" followed by
>> "darcs send -o mypatch", although in the general case I prefer plain
>> diffs.
>
> OK - here's a patch produced as above.
Thank you, this one applies.
But the patch is very cluttered since it's full of