git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sam Ravnborg <sam@ravnborg.org>
To: Bradford Smith <bradford.carl.smith@gmail.com>
Cc: David Kastrup <dak@gnu.org>, git@vger.kernel.org
Subject: Re: Shell script cleanups/style changes?
Date: Thu, 2 Aug 2007 20:13:15 +0200	[thread overview]
Message-ID: <20070802181315.GE2431@uranus.ravnborg.org> (raw)
In-Reply-To: <f158199e0708020748o5cac4505ic76bfb39f25ab1f8@mail.gmail.com>

> 
> Obviously, you aren't too concerned about 1 (the cost to you), because
> you're willing to do that work.  However, if I were Junio, I wouldn't
> be willing to "spend" costs 2 and 3 on a patch that didn't either fix
> a problem or provide a new feature.

For any decent codebase there is a need to keep the code clean.
Being part of the linux-kernel community we see clean-up patches 
each day and a lot are applied.
Even spelling errors in comments are sometimes applied.

Do not underestimate the value of a clean codebase.

	Sam

  reply	other threads:[~2007-08-02 18:12 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-08-02 10:44 Shell script cleanups/style changes? David Kastrup
2007-08-02 14:00 ` Robert Schiele
2007-08-02 14:20   ` David Kastrup
2007-08-02 16:19     ` Robert Schiele
2007-08-02 17:05       ` Johannes Schindelin
2007-08-02 17:22         ` Robert Schiele
2007-08-03 19:29     ` Uwe Kleine-König
2007-08-02 14:48 ` Bradford Smith
2007-08-02 18:13   ` Sam Ravnborg [this message]
2007-08-02 20:37 ` Junio C Hamano
2007-08-02 20:56   ` Nguyen Thai Ngoc Duy
2007-08-02 21:02     ` David Kastrup
2007-08-02 21:12     ` Junio C Hamano
2007-08-02 20:57   ` David Kastrup
2007-08-02 21:21     ` Junio C Hamano
2007-08-02 21:29       ` Junio C Hamano
2007-08-02 22:02         ` David Kastrup
2007-08-02 21:41       ` Robert Schiele
2007-08-02 22:14         ` David Kastrup
2007-08-02 23:05           ` Junio C Hamano
2007-08-02 23:17             ` David Kastrup
2007-08-03  0:12               ` Junio C Hamano
2007-08-03  0:24                 ` David Kastrup
2007-08-03  0:48                   ` Junio C Hamano
2007-08-03  6:06                     ` David Kastrup
2007-08-03  7:41                       ` Junio C Hamano
2007-08-03  8:41                         ` David Kastrup
2007-08-03  6:13                     ` David Kastrup
2007-08-03  2:28                   ` Robert Schiele
2007-08-03  6:08                     ` David Kastrup
2007-08-02 23:21             ` Robert Schiele
2007-08-02 23:32               ` David Kastrup
2007-08-02 23:45                 ` Robert Schiele
2007-08-02 23:52                   ` David Kastrup
2007-08-03  0:01                     ` Robert Schiele
2007-08-03  0:11                       ` David Kastrup
2007-08-03  7:11                         ` Junio C Hamano
2007-08-02 23:27           ` Robert Schiele
2007-08-04  7:10         ` Florian Weimer
2007-08-04 20:32           ` Robert Schiele
2007-08-04 20:39             ` Junio C Hamano
2007-08-02 21:42       ` David Kastrup

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=20070802181315.GE2431@uranus.ravnborg.org \
    --to=sam@ravnborg.org \
    --cc=bradford.carl.smith@gmail.com \
    --cc=dak@gnu.org \
    --cc=git@vger.kernel.org \
    /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).