This is an automated email from the git hooks/post-receive script. It was
generated because a ref change was pushed to the repository containing
the project "Gem".

The branch, 0.93 has been updated
       via  074f44f76e96cb7222168d991a6c729331b84046 (commit)
       via  a7449320563007adc2fca96f24d49fe71d7c6581 (commit)
      from  f36ac41f22ccdc965cb9acaacbd3a4f435555916 (commit)

Those revisions listed above that are new to this repository have
not appeared on any other notification email; so we list those
revisions in full, below.

- Log -----------------------------------------------------------------
commit 074f44f76e96cb7222168d991a6c729331b84046
Author: zmoelnig <zmoelnig@tigital.iemnet>
Date:   Wed Nov 30 15:29:03 2011 +0100

    imageQT: convert to RGBA image before saving
    
    picked from master
    resolved conflicts

commit a7449320563007adc2fca96f24d49fe71d7c6581
Author: zmoelnig <zmoelnig@tigital.iemnet>
Date:   Wed Nov 30 14:29:41 2011 +0100

    got refcounting work properly
    
    *refcount++ is a POOR choice, as it will increment the pointer, rather than 
the value.
    instead we now use:
     ++*refcount;
     --*refcount;
    
    this also get's rid of a warning on OSX about freeing unaligned memory

-----------------------------------------------------------------------

Summary of changes:
 plugins/imageQT/imageQT.cpp |   16 +++++++++-------
 src/Gem/ThreadMutex.cpp     |    5 ++---
 2 files changed, 11 insertions(+), 10 deletions(-)


hooks/post-receive
-- 
Gem

------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure 
contains a definitive record of customers, application performance, 
security threats, fraudulent activity, and more. Splunk takes this 
data and makes sense of it. IT sense. And common sense.
http://p.sf.net/sfu/splunk-novd2d
_______________________________________________
pd-gem-CVS mailing list
pd-gem-CVS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/pd-gem-cvs

Reply via email to