Re: [Chicken-hackers] [PATCH] mutex-lock! sometimes not srfi-18 compliant

2015-11-23 Thread Jörg F . Wittenberger
Sorry, this patch needs a patch. Looks like I shot myself into the foot (using git) again the very same way. (Looks like "git add" caches the changes, thus must be given not once per file but once I'm done changing things.) Now I'm a bit lost. How would I format a proper patch for git with

Re: [Chicken-hackers] [PATCH] mutex-lock! sometimes not srfi-18 compliant

2015-11-23 Thread John Cowan
Jörg F. Wittenberger scripsit: > Looks like I shot myself into the foot (using git) again the very same > way. (Looks like "git add" caches the changes, thus must be given not > once per file but once I'm done changing things.) As long as all your changes are going into a single patch, avoiding

[Chicken-hackers] [PATCH] mutex-lock! sometimes not srfi-18 compliant

2015-11-23 Thread Jörg F . Wittenberger
Hi all, Am 07.11.2015 um 21:55 schrieb "Jörg F. Wittenberger": > Hi, > > try the test case: looks like I messed up with this one. (I sent out half the patch.) Attached a better version. This one adds a test case which actually fails until chicken is recompiled. Best /Jörg >From