metron-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From mattf-horton <>
Subject [GitHub] incubator-metron pull request #502: METRON-814 minor tweaks in document form...
Date Sat, 01 Apr 2017 00:13:32 GMT
GitHub user mattf-horton opened a pull request:

    METRON-814 minor tweaks in document format of

    ## Contributor Comments
    Apparently github ate my latest comment on PR#497. Here's the fix that would have been
    In metron-deployment/vagrant/ , numbered list items 7a and 20 display
incorrectly in Github-MD. This patch makes them right in both Github-MD and doxia-markdown,
and makes item 8 consistent even tho it doesn't affect the display.
    ## Pull Request Checklist
    - [x] Is there a JIRA ticket associated with this PR? If not one needs to be created at
[Metron Jira](

    - [x] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are
trying to resolve? Pay particular attention to the hyphen "-" character.
    - [x] Has your PR been rebased against the latest commit within the target branch (typically
    ### For code changes: NA
    ### For documentation related changes:
    - [x] Have you ensured that format looks appropriate for the output in which it is rendered
by building and verifying the site-book? 

You can merge this pull request into a Git repository by running:

    $ git pull METRON-804b

Alternatively you can review and apply these changes as the patch at:

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #502
commit ed247c7a3d61d5779b72915d2c7e8f370a52a47f
Author: mattf-horton <>
Date:   2017-03-31T23:52:33Z

    METRON-814 minor tweaks in document format of


If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at or file a JIRA ticket
with INFRA.

View raw message