I do feel that starting a conversation with an email to discuss the what
and why is better than just a line item on an Agenda without other context.
We do intend to keep minutes. To date most of the stuff was just getting
prep work done for the sprint, vs discussing policy among the teams.
John
=:
I think this has come up before on this list, but: isn't having 2 sets of
commands in the first place a design smell? If we need aliases because users
aren't using the originals, then shouldn't we fix the original commands?
Tim Penhey writes:
> On 25/05/16 00:12, Marco Ceppi wrote:
>> Even i
The change is merging as we speak, so if you have scripts etc that need to
be updated, do so before pulling master.
--
Juju-dev mailing list
Juju-dev@lists.ubuntu.com
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/juju-dev
Where was this discussed?
On Wed, May 25, 2016, 10:56 AM Nate Finch wrote:
> The change is merging as we speak, so if you have scripts etc that need to
> be updated, do so before pulling master.
> --
> Juju-dev mailing list
> Juju-dev@lists.ubuntu.com
> Modify settings or unsubscribe at:
> https
I believe it was discussed at the Vancouver sprint.
On Wed, May 25, 2016 at 12:09 PM Adam Stokes
wrote:
> Where was this discussed?
>
> On Wed, May 25, 2016, 10:56 AM Nate Finch
> wrote:
>
>> The change is merging as we speak, so if you have scripts etc that need
>> to be updated, do so before
+1 ... one and only one way to do something is a lot easier to understand.
Either we like juju list-foos or we like juju foos... pick one and move
on. This feels like two camps agreed to disagree and just kept both.
On Wed, May 25, 2016 at 10:12 AM Katherine Cox-Buday <
katherine.cox-bu...@canoni
Hi Phani,
Is the key used for the machine known to juju? You can view the ssh keys
with `juju authorized-keys list` for juju 1.x, and `juju list-ssh-keys` for
juju 2.0.
If it's not there, you can use the following commands to add the key and
juju will try to use it when connecting to the machine
