tes/pull/471
Thanks!
--
Ben Ford
@binford2k
Community & DevRel Lead
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubscr...@googleg
ted.
So long, old friend!
--
Ben Ford
@binford2k
Ecosystem Product Manager
--
You received this message because you are subscribed to the Google Groups
"Puppet Developers" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to puppet-dev+unsubsc
Could you write up an example of what kind of code would have the
conditions reversed so that we can share with community members that might
be affected?
On Wed, Dec 12, 2018 at 2:48 PM Kris Bosland
wrote:
> Forwarding this to the developer group - does anyone have any feedback on
> this change?
Has Puppet made your life easier like it's made my life easier? Come hang
out on Dec. 7 with other community members, Vox Pupuli, and Puppet
employees to hack on awesome Puppet (and related) projects. Let's get to
know each other!
http://pup.pt/hack
#puppethack is a collaborative, relaxed online
een made yet.
>
> - henrik
>
> --
>
> Visit my Blog "Puppet on the Edge"
> http://puppet-on-the-edge.blogspot.se/
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet Developers" group.
> To unsubsc
On Tue, Oct 14, 2014 at 8:57 AM, Henrik Lindberg <
henrik.lindb...@cloudsmith.com> wrote:
> On 2014-14-10 17:36, Ben Ford wrote:
>
>> I have to admit that this email made me feel a little bit dumb. Could
>> you provide a TL;DR summary that at least provides a little cont
track down a memory leak in
> the future...
>
> Regards
> - henrik
>
>
> --
>
> Visit my Blog "Puppet on the Edge"
> http://puppet-on-the-edge.blogspot.se/
>
> --
> You received this message because you are subscribed to the Google Groups
> "Puppet De
ce=footer>
> .
>
> For more options, visit https://groups.google.com/d/optout.
>
--
Ben Ford | Training Solutions Engineer
Puppet Labs, Inc.
926 NW 13th Ave, Suite #210
Portland, OR 97209
509.592.7291
ben.f...@puppetlabs.com
--
You received this message because you are subscri
@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/puppet-dev/1d05d805-edfd-40a0-a651-c13aab943270%40googlegroups.com
> <https://groups.google.com/d/msgid/puppet-dev/1d05d805-edfd-40a0-a651-c13aab943270%40googlegroups.com?utm_medium
> email to puppet-dev+unsubscr...@googlegroups.com.
>> To view this discussion on the web visit
>> https://groups.google.com/d/msgid/puppet-dev/CAEXKxLz_%3DN8i%3D416YpQX%2B3-2TydtSVZLoaa43Hff41XeyHsb9g%40mail.gmail.com
>> <https://groups.google.com/d/msgid/puppet-dev/CAEXKxLz_%3DN8i%3D416YpQX%2B3-2TydtSVZLoaa4
this message because you are subscribed to the Google
>> Groups "Puppet Developers" group.
>> To unsubscribe from this group and stop receiving emails from it, send
>> an email to puppet-dev+unsubscr...@googlegroups.com
>> <mailto:puppet-dev+unsubscr...@googleg
I don't think we have the luxury of backing them out any more; and to be
honest I think that these functions here are mostly OK. Map & filter will
be fine. People will struggle with reduce and slice and they probably won't
get used much.
I have two real concerns here. Clearly I'm concerned abou
I really like the metaparameter approach. It's almost self documenting.
On Tuesday, August 5, 2014 6:41:40 PM UTC-7, Reid Vandewiele wrote:
>
> Maybe solving for this use case would be better handled by implementing
> something that looks and feels like a metaparameter rather than trying to
>
13 matches
Mail list logo
