On Tue, Oct 8, 2013 at 9:44 AM, Thomas Maddox
wrote:
> On 10/7/13 3:49 PM, "Doug Hellmann" wrote:
>
>
>
>
> On Mon, Oct 7, 2013 at 4:23 PM, Thomas Maddox > wrote:
>
>> On 10/7/13 1:55 PM, "Doug Hellmann"
>> wrote:
>>
>>
>>
>>
>> On Mon, Oct 7, 2013 at 1:44 PM, Thomas Maddox <
>> thomas.mad.
On 10/7/13 3:49 PM, "Doug Hellmann"
mailto:doug.hellm...@dreamhost.com>> wrote:
On Mon, Oct 7, 2013 at 4:23 PM, Thomas Maddox
mailto:thomas.mad...@rackspace.com>> wrote:
On 10/7/13 1:55 PM, "Doug Hellmann"
mailto:doug.hellm...@dreamhost.com>> wrote:
On Mon, Oct 7, 2013 at 1:44 PM, Thomas
On Mon, Oct 7, 2013 at 4:23 PM, Thomas Maddox
wrote:
> On 10/7/13 1:55 PM, "Doug Hellmann" wrote:
>
>
>
>
> On Mon, Oct 7, 2013 at 1:44 PM, Thomas Maddox > wrote:
>
>> On 10/3/13 4:09 PM, "Thomas Maddox" wrote:
>>
>> >On 10/3/13 8:53 AM, "Julien Danjou" wrote:
>> >
>> >>On Thu, Oct 03 2013,
On 10/7/13 1:55 PM, "Doug Hellmann"
mailto:doug.hellm...@dreamhost.com>> wrote:
On Mon, Oct 7, 2013 at 1:44 PM, Thomas Maddox
mailto:thomas.mad...@rackspace.com>> wrote:
On 10/3/13 4:09 PM, "Thomas Maddox"
mailto:thomas.mad...@rackspace.com>> wrote:
>On 10/3/13 8:53 AM, "Julien Danjou"
>ma
On Mon, Oct 7, 2013 at 1:44 PM, Thomas Maddox
wrote:
> On 10/3/13 4:09 PM, "Thomas Maddox" wrote:
>
> >On 10/3/13 8:53 AM, "Julien Danjou" wrote:
> >
> >>On Thu, Oct 03 2013, Thomas Maddox wrote:
> >>
> >>> Interesting point, Doug and Julien. I'm thinking out loud, but if we
> >>>wanted
> >>> to
On 10/3/13 4:09 PM, "Thomas Maddox" wrote:
>On 10/3/13 8:53 AM, "Julien Danjou" wrote:
>
>>On Thu, Oct 03 2013, Thomas Maddox wrote:
>>
>>> Interesting point, Doug and Julien. I'm thinking out loud, but if we
>>>wanted
>>> to use pipeline.yaml, we could have an 'enabled' attribute for each
>>> p
On 10/3/13 8:53 AM, "Julien Danjou" wrote:
>On Thu, Oct 03 2013, Thomas Maddox wrote:
>
>> Interesting point, Doug and Julien. I'm thinking out loud, but if we
>>wanted
>> to use pipeline.yaml, we could have an 'enabled' attribute for each
>> pipeline?
>
>That would be an option, for sure. But ju
On Thu, Oct 03 2013, Thomas Maddox wrote:
> Interesting point, Doug and Julien. I'm thinking out loud, but if we wanted
> to use pipeline.yaml, we could have an 'enabled' attribute for each
> pipeline?
That would be an option, for sure. But just removing all of them should
also work.
> I'm curio
On 10/3/13 8:15 AM, "Doug Hellmann"
mailto:doug.hellm...@dreamhost.com>> wrote:
On Thu, Oct 3, 2013 at 5:54 AM, Julien Danjou
mailto:jul...@danjou.info>> wrote:
On Wed, Oct 02 2013, Thomas Maddox wrote:
> I'm working to make the sample pipeline optional and I'm stuck at a
> decision point ab
On Thu, Oct 3, 2013 at 5:54 AM, Julien Danjou wrote:
> On Wed, Oct 02 2013, Thomas Maddox wrote:
>
> > I'm working to make the sample pipeline optional and I'm stuck at a
> > decision point about whether I ought to use a collector config option
> > (like 'enable_sample_pipelines'), or let it be d
On Wed, Oct 02 2013, Thomas Maddox wrote:
> I'm working to make the sample pipeline optional and I'm stuck at a
> decision point about whether I ought to use a collector config option
> (like 'enable_sample_pipelines'), or let it be driven by setup.cfg (i.e.
> the existence of sample plugin refere
Hey All!
I'm working to make the sample pipeline optional and I'm stuck at a
decision point about whether I ought to use a collector config option
(like 'enable_sample_pipelines'), or let it be driven by setup.cfg (i.e.
the existence of sample plugin references). My favorite right now is the
forme
12 matches
Mail list logo
