I'll see if I can figure all that out and test this weekend... I assume with git log it will be obvious what commit I need to cherry-pick.
-John
On Wed, Apr 4, 2012 at 2:08 AM, IOhannes m zmoelnig zmoelnig@iem.at wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
On 2012-04-04 03:25, Hans-Christoph Steiner wrote:
i have hopefully fixed that as well and committed it to Gem's git
(committish 1458b4f8cf in the 0.93 branch, in case somebody wants to backport it)
John or IOhannes,
Please let me know when its in the 0.93 branch, and I'll include it in
Pd-extended.
"committed it to Gem's git (committish 1458b4f8cf in the 0.93 branch)"
it would be nice, if john could test it more directly, without having me fix the bug in Gem's master, then backport it to Gem's 0.93, then having hans backport the changes to Pd-extended, then wait for the nightly build and then report that it is not working...
backporting from Gem's master to Gem's 0.93 is fairly trivial using git's cherry-pick. the rest is less fun and should probably only be done once the bug is really fixed.
fmasdr IOhannes -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk9781EACgkQkX2Xpv6ydvTGPwCfW9oHv5Cwl0YHmUqvnLYjoe7N e0YAoNn2ES0T6jha+hvYXy1IsmxGFZUJ =NZrN -----END PGP SIGNATURE-----
Pd-list@iem.at mailing list UNSUBSCRIBE and account-management -> http://lists.puredata.info/listinfo/pd-list