Mailing-List: contact issues-help@mesos.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@mesos.apache.org
Date: Fri, 13 Mar 2015 16:33:39 +0000 (UTC)
From: "Alexander Rojas (JIRA)" <jira@apache.org>
To: issues@mesos.apache.org
Message-ID: <JIRA.12781836.1426261502000.86751.1426264419563@Atlassian.JIRA>
In-Reply-To: <JIRA.12781836.1426261502000@Atlassian.JIRA>
References: <JIRA.12781836.1426261502000@Atlassian.JIRA>
 <JIRA.12781836.1426261502744@arcas>
Subject: [jira] [Commented] (MESOS-2496) Make description consistent when
 adding flags
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


    [ https://issues.apache.org/jira/browse/MESOS-2496?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14360589#comment-14360589 ] 

Alexander Rojas commented on MESOS-2496:
----------------------------------------

I like the idea of having a line break after every description. It creates a visual boundary between flags.

> Make description consistent when adding flags
> ---------------------------------------------
>
>                 Key: MESOS-2496
>                 URL: https://issues.apache.org/jira/browse/MESOS-2496
>             Project: Mesos
>          Issue Type: Task
>            Reporter: Joerg Schad
>            Assignee: Joerg Schad
>            Priority: Minor
>
> When adding flags in slave/flags.hpp or master/flags.hpp we are inconsistent in adding newline at the end of the the description. For example mesos-slave.sh --help sometimes has a empty line between flags and sometimes not.
> Personally I like extra empty line between flags as it makes the help text more readable, but most importantly we should have this consistent.
> Actually other tools such as gcc do not have newlines between flags.


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)