[M3devel] pthreads committed to git

Dragiša Durić dragisha at m3w.org
Tue Aug 26 18:52:25 CEST 2014

There is also some webhooks mechanism. We can work on webhook -> e-mail later on.


On 26 Aug 2014, at 11:01, dragisha at m3w.org wrote:

> You can see on github what went through. There are some RSS feed to be used for notification automation, no emails as far as I can see.
> To ensure changes are commited, you need to "git add" changed files, and then "git commit" added files. After that "git push" will finish this. You can first "git add" all changed files, of course, and this way all will go through as single commit.
> There can be a conflict at "git push" in case someone did something conflicting with your changes remotely. Not right now, most probably, and you just need to do a "git pull" before "git push" to do merge locally. As I said, right now this will most probably be without conflict - not many people are changing.
> I will try to explain workflows as soon as I get some time.
> dd
> On 26.08.2014 09:52, mika at async.caltech.edu wrote:
>> Hi m3devel,
>> I just pushed---I think---the fixed version of ThreadPThread.m3 to github.
>> There is no m3commit email from this?
>> I (and I'm sure Tony too) am very curious to hear if this makes things
>> worse on any OS.  (E.g., if it causes the pthreads to freeze.)  It works
>> perfectly on my AMD64_LINUX system: fork, memory allocation, everything.
>> Now to figure out whether the garbage collector bits can be sped up a bit.
>>     Mika

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 495 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://m3lists.elegosoft.com/pipermail/m3devel/attachments/20140826/6d9de43f/attachment-0002.sig>

More information about the M3devel mailing list