Open Stack

Absolute paths often depend on distribution packages (as much as they
should follow upstream), which we try to avoid beyond the installation
guide. Also, absolute paths can become lengthy and seem unnecessary for
guides with more advanced audiences who know where to find common
configuration files. Frankly, we should focus our efforts on contributing
content rather than patches that accomplish little more than increasing
Stackalytics numbers.

On Tue, Aug 2, 2016 at 10:47 AM, Anne Gentle <annegentle at justwriteclick.com>
wrote:

>
>
> On Sun, Jul 31, 2016 at 6:53 PM, chen.xing at 99cloud.net <
> chen.xing at 99cloud.net> wrote:
>
>> Hi all,
>>
>> I found there many place indicates the configuration file like " in the
>> ``nova.conf``file " or " in the ``neutron.conf`` file ". But some commits
>> to change these file path to absolute path.
>> Should we need to change all path to absolute path?
>>
>>
> I have been approving changes without a bug link that contain only
> absolute path as a change.
>
> That said, I think this can be a "rolling change" and does not need to
> happen across all deliverables, especially since we have a filename change
> going on now.
>
> Thanks for asking -
> Anne
>
>
>> Thanks,
>>
>> Chason Chan
>>
>>
>>
>> _______________________________________________
>> OpenStack-docs mailing list
>> OpenStack-docs at lists.openstack.org
>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>>
>>
>
>
> --
> Anne Gentle
> www.justwriteclick.com
>
> _______________________________________________
> OpenStack-docs mailing list
> OpenStack-docs at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-docs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-docs/attachments/20160802/01d23665/attachment.html>