-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 > We do want to re-enable this functionality, and we will get back around to > it. In the meantime, we'd more than welcome any patches regarding this.
Ok, thanks for the explanation. I didn't know about that in-house rule. Though, I have to admit that to me this looks like a weird rule. But: I don't really want to discuss your internal development processes here. Actually, I suspected something like that. However, I still think that with a rule like that, it's quite easy that something will fall under the table, especially as it have been already merged for a little while (longer than 4 hours), so from my far distance it's only about making the tests green... ;) And as I know that a couple of people are waiting for that feature to be in the core, I'm a bit nitpicking here. So this is why I jumped in and barked around. Hope you don't mind?! Regarding fixing the problem: The tests ran fine on my machine (TM), but yeah, intermittent can be hard to debug and track down. However, as I don't really know more about your problems, I can only start with wild guesses that wouldn't be very helpful. ~pete -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.11 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAk47AD8ACgkQbwltcAfKi38oFgCeMLypMBIUKMyPp5n6Q9MlumjN JW0AoKRewsJWDhPLI5TWVFuAsgB7iC0j =yKby -----END PGP SIGNATURE----- -- You received this message because you are subscribed to the Google Groups "Puppet Developers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/puppet-dev?hl=en.
