Greetings,
the following patch (which is never meant to be committed, and is therefore
very ugly in purpose) is a proof of concept for an alternative to the recent
problematic feature proposal of returning failure status for gmond and that
is part of 3.1.3^H4^H5.
it has been tested on Linux
On Wed, Dec 02, 2009 at 07:41:39PM +, Daniel Pocock wrote:
Therefore, the approach might need to be some combination of the
solutions. E.g. a configure option that allows people to choose the new
behaviour or the old behaviour.
-1, this will double our supported paths for almost no
Jesse
There is a backport request for 3.1 labeled build: remove ganglia release
name from the code and that has a veto from you which I would like to see
reconsidered.
your objection refers to a thread[1] that includes the explanation of why
this backport proposal is consistent with the
Hi folks,
my comment to that thread still stays [1], and I do not think that coming up
with a name is so difficult that it actually can block a release (seems 3.1.x
has bigger problems than that :-). But it really seems to be used nowhere (I
thought the name was displayed on the web page ?),
On Thu, Dec 3, 2009 at 07:44, Carlo Marcelo Arenas Belon
care...@sajinet.com.pe wrote:
Jesse
There is a backport request for 3.1 labeled build: remove ganglia release
name from the code and that has a veto from you which I would like to see
reconsidered.
I've removed my objection (r2136).
