Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 29 Nov 2012 03:44:50 +0100
From:      Emanuel Haupt <ehaupt@FreeBSD.org>
To:        Alexey Dokuchaev <danfe@FreeBSD.org>
Cc:        svn-ports-head@FreeBSD.org, svn-ports-all@FreeBSD.org, Emanuel Haupt <ehaupt@FreeBSD.org>, ports-committers@FreeBSD.org
Subject:   Re: svn commit: r307951 - head/sysutils/sleuthkit
Message-ID:  <20121129034450.f0d1802f0dd0c5c2396d1ebd@FreeBSD.org>
In-Reply-To: <20121129020924.GC11624@FreeBSD.org>
References:  <201211290020.qAT0Kecl058401@svn.freebsd.org> <20121129020924.GC11624@FreeBSD.org>

next in thread | previous in thread | raw e-mail | index | archive | help
Alexey Dokuchaev <danfe@FreeBSD.ORG> wrote:
> On Thu, Nov 29, 2012 at 12:20:40AM +0000, Emanuel Haupt wrote:
> > New Revision: 307951
> > URL: http://svnweb.freebsd.org/changeset/ports/307951
> > 
> > Log:
> >   - Update to 4.0.1
> >   - Take maintainership
> >   - Remove double spaces from pkg-descr and 'fmt -w 80'
> 
> Emanuel,
> 
> We at FreeBSD do prefer double spaces, and previously port description
> was nicely indented and formatted (as it was my port).  Now it looks
> considerably worse.  May I ask you to backout pkg-descr change?

I would say this is opinionated. I think it looks better that way. I've
always removed double spaces (which most of the time were introduced
trough copy pasting from webpages/manpages) in the past.

Even the PHB (3.2.1, grey box) suggests so:

--- begin quote --- 
Please be careful if you are copying from the README or manpage; too
often they are not a concise description of the port or are in an
awkward format (e.g., manpages have justified spacing).
--- end quote --- 

Emanuel



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20121129034450.f0d1802f0dd0c5c2396d1ebd>