git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: Wincent Colaiuta <win@wincent.com>
Cc: Git Mailing List <git@vger.kernel.org>, Junio Hamano <junkio@cox.net>
Subject: Re: [PATCH] Add line-wrapping guidelines to the coding style documentation
Date: Wed, 14 Nov 2007 17:19:27 +0000 (GMT)	[thread overview]
Message-ID: <Pine.LNX.4.64.0711141717570.4362@racer.site> (raw)
In-Reply-To: <56A87A65-3C2E-4E10-84D4-4470879EE466@wincent.com>

Hi,

On Wed, 14 Nov 2007, Wincent Colaiuta wrote:

> Help new contributors by providing some advice about line-wrapping; the 
> advice basically boils down to "use 80-characters minus some slop as a 
> rule of thumb", but also "use common sense", and "avoid gratuitous 
> rewrapping".

We already have this:

 - We try to keep to at most 80 characters per line.

Besides, is it really necessary to be as explicit as you word it?  IOW is 
this patch needed?

Because if we go down that road, we might very well end up with a 
CodingGuidelines document that is larger than git's source code.

Ciao,
Dscho

  parent reply	other threads:[~2007-11-14 17:20 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-14 10:19 [PATCH] Add line-wrapping guidelines to the coding style documentation Wincent Colaiuta
2007-11-14 10:37 ` Junio C Hamano
2007-11-14 17:19 ` Johannes Schindelin [this message]
2007-11-14 19:00   ` [PATCH v3] " Wincent Colaiuta
2007-11-14 19:08     ` Andreas Ericsson
2007-11-14 20:04     ` Junio C Hamano
2007-11-14 20:23       ` Wincent Colaiuta

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.LNX.4.64.0711141717570.4362@racer.site \
    --to=johannes.schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    --cc=win@wincent.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).