-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Joe Auty wrote: > Greg, > > After applying the update (which I noticed was available immediately > after my last response to you, sorry about that!), everything is just > peachy now, or at least not causing the segfaults, thanks! > > Not to sound unappreciative and purely in the spirit of being > constructive, I'd suggest a little more specificity as far as what a > "break" is on the commit history. This goofy title was created because > it didn't occur to me that the break fix committed on April 12 was only > for compilation. I would suggest specifying whether the break and the > fix is for compiling, or for the software to work properly > post-compilation. This would have saved me a little confusion and time. > > > Again, you kick ass, in no way do I want this to sound harshly critical, > I hope this can be taken as purely constructive :) > > Thanks again for your help with this fix! >
Hi Joe, Great, I'm glad to hear that's working for you now. I do appreciate your input, re: commit logs. "Unbreak" is too nebulous, and I'll plan to add further info like "fixed compiler error" in the future. I admit we were in a bit of a rush to get various PHP modules building again after the PHP 5.3.2 update, and I somehow missed the fact that this one supported 5.3.2 with a new release of itself. I think I'll be better prepared for this kind of thing in the future! Regards, Greg - -- Greg Larkin http://www.FreeBSD.org/ - The Power To Serve http://www.sourcehosting.net/ - Ready. Set. Code. http://twitter.com/sourcehosting/ - Follow me, follow you -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.7 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iD8DBQFLzf7v0sRouByUApARAockAKC61isslQlss2C03zRPbovtBG6H9QCgkOFE g2xUYqmTQvdFXZibSEgi5A0= =qfdq -----END PGP SIGNATURE----- _______________________________________________ [email protected] mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to "[email protected]"
