Displaying 6 results from an estimated 6 matches for "misphrased".
2013 Sep 05
1
best practice
...the
puppet agent from running automatically and instead require a manual command for puppet to exercise on that node.
If it is as simple as
puppet apply path-to-pp
with the puppet agent up but somehow disabled for automatic operation, I can work with that or equivalent. Forgive me if I have misphrased the syntax.
I am asking you how you did that.
This is for deployments of software
which are manually extremely intensive.
Thanks.
--
You received this message because you are subscribed to the Google Groups "Puppet Users" group.
To unsubscribe from this group and stop receiving e...
2018 Jan 03
2
Distinguishing trunk version number from release
...om
> <mailto:jyknight at google.com>> wrote:
>
> I'd like to propose that trunk always have a version number which
> is in between versions used by the previous release branch, and
> before the versions used in the next release branch.
>
>
> Oops, I misphrased that -- I meant to say "which is /after/ versions
> used by the previous release branch, and before the versions used in
> the next release branch."
>
>
> Right now, trunk is sharing the 7.0.0 number, which will also be
> used by the next release 4 months from...
2018 Jan 03
0
Distinguishing trunk version number from release
...Wed, Jan 3, 2018 at 12:24 PM, James Y Knight <jyknight at google.com> wrote:
> I'd like to propose that trunk always have a version number which is in
> between versions used by the previous release branch, and before the
> versions used in the next release branch.
>
Oops, I misphrased that -- I meant to say "which is *after* versions used
by the previous release branch, and before the versions used in the next
release branch."
> Right now, trunk is sharing the 7.0.0 number, which will also be used by
> the next release 4 months from now. Since some people use a...
2018 Jan 03
0
Distinguishing trunk version number from release
...at 12:24 PM, James Y Knight <jyknight at google.com<mailto:jyknight at google.com>> wrote:
I'd like to propose that trunk always have a version number which is in between versions used by the previous release branch, and before the versions used in the next release branch.
Oops, I misphrased that -- I meant to say "which is after versions used by the previous release branch, and before the versions used in the next release branch."
Right now, trunk is sharing the 7.0.0 number, which will also be used by the next release 4 months from now. Since some people use and release sn...
2018 Jan 03
8
Distinguishing trunk version number from release
I'd like to propose that trunk always have a version number which is in
between versions used by the previous release branch, and before the
versions used in the next release branch.
Right now, trunk is sharing the 7.0.0 number, which will also be used by
the next release 4 months from now. Since some people use and release
snapshots of clang from trunk (e.g. the Android NDK), it'd be
1998 Aug 05
6
IP Security for Linux (IPSec)
I''ve kept this one on the back burner for a while, waiting for it to
mature before attempting to use it, and now having seen OpenBSD
ship with IPSec I''m getting a bit impatient =).
What is the status of IPSec for Linux (and more specifically RedHat)?
By this I mean I just did some www browsing/etc and found about a
half dozen different implimentations, ranging from NRL, to a