Displaying 4 results from an estimated 4 matches for "unapproachable".
Did you mean:
approachable
2006 Mar 10
2
Date and Times a la Dalgaard
...ource for learning the basics of how to manage and
manipulate dates and times in R? I have been reading "Introductory
Statistics with R" by Peter Dalgaard which is fantastic. But alas, I could
find no reference to date and time. I have looked at the reference manual
but it is particularly unapproachable. So rather than dense technical talk I
would rather see a dataset, several arguments and commentary of what is
happening. The alternative to is to make Excel or Microsoft Access handle
all the date and time work (I have had about 16 years experience with how to
calculate and handle date and time in...
2018 Sep 26
0
Re: OpenStack output workflow
...satile and proposes a lot of options for input and
> output. The downside of it is that over time is becomes more and
> more difficult to know them all.
The options are all documented in the manual. I have thought for a
while that we need to tackle the virt-v2v manual: It's too big, and
unapproachable. Really I think we need to split it into topic
sections and rewrite parts of it. Unfortunately I've not had time to
do that so far.
> And all the error messages are made for human beings, not machines,
> so providing feedback through a launcher, such as virt-v2v-wrapper,
> is diffic...
2018 Sep 26
2
Re: OpenStack output workflow
[Adding Tomas Golembiovsky]
On Wed, Sep 26, 2018 at 12:11 PM Richard W.M. Jones <rjones@redhat.com>
wrote:
>
> Rather than jumping to a solution, can you explain what the problem
> is that you're trying to solve?
>
> You need to do <X>, you tried virt-v2v, it doesn't do <X>, etc.
>
Well, that's mainly IMS related challenges. We're working on
2018 Sep 26
3
Re: OpenStack output workflow
...options for input and
> > output. The downside of it is that over time is becomes more and
> > more difficult to know them all.
>
> The options are all documented in the manual. I have thought for a
> while that we need to tackle the virt-v2v manual: It's too big, and
> unapproachable. Really I think we need to split it into topic
> sections and rewrite parts of it. Unfortunately I've not had time to
> do that so far.
>
> > And all the error messages are made for human beings, not machines,
> > so providing feedback through a launcher, such as virt-v2v...