For reference, I'm fine with either, provided it's thought through or
even better ... consistent :)
Assisting troubleshooting is an important role, and an "anemic" chapter
is a sad, sad thing :)
Of course, with our excellent re-use-loving structuring of chapters, it
should be possible to eve
I like troubleshooting info very close to the topic it addresses. It's also
good to pull common errors into one place.
Anne Gentle
Content Stacker
a...@openstack.org
On Jul 12, 2012, at 9:45 AM, Lorin Hochstein wrote:
> (crossposting to doc-core in case not everyone there has moved over to
>
On 07/12/2012 10:45 AM, Lorin Hochstein wrote:
> (crossposting to doc-core in case not everyone there has moved over to
> openstack-docs yet).
>
> A question came up on this merge proposal: https://review.openstack.org/9494
>
> In that proposal, I had created a "troubleshooting" section in the
>
(crossposting to doc-core in case not everyone there has moved over to
openstack-docs yet).
A question came up on this merge proposal: https://review.openstack.org/9494
In that proposal, I had created a "troubleshooting" section in the Networking
chapter in the Compute Admin guide. Tom pointed
4 matches
Mail list logo
