Bug 1470928 - Review strategy for using file names in titles
Review strategy for using file names in titles
Status: NEW
Product: GLS Content Services
Classification: Internal
Component: Standards, References, and Guides (Show other bugs)
unspecified
Unspecified Unspecified
low Severity low
: ---
: ---
Assigned To: David O'Brien
klaatu
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-13 23:02 EDT by David O'Brien
Modified: 2017-07-27 02:52 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description David O'Brien 2017-07-13 23:02:25 EDT
Description of problem:

Feedback from course DO407:

<formalpara>
     <title>Using <filename>/etc/ansible/ansible.cfg</filename></title>

<!-- TechEditor: Try to avoid using file names and tags in titles. Perhaps "Configuring Ansible with the Default Configuration File"? -->


Title done in this way based on feedback for the Ansible 2.0 revision to make clearer the actual file names being referenced. Not eager to open this can of worms again with yet another rework.


If this classifies as a GLS requirement in some areas we can allow for it, and document how it works. If it's based on feedback then it's obviously a valid concern. I'll raise an RFE.


Expected results:


Additional info:

Note You need to log in before you can comment on or make changes to this bug.