All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rene Scharfe <rene.scharfe@lsrfire.ath.cx>
To: Geert Bosch <bosch@adacore.com>
Cc: Git Mailing List <git@vger.kernel.org>, Junio C Hamano <junkio@cox.net>
Subject: Re: RFC: New diff-delta.c implementation
Date: Tue, 25 Apr 2006 20:22:23 +0200	[thread overview]
Message-ID: <444E68DF.1020105@lsrfire.ath.cx> (raw)
In-Reply-To: <20060424025741.GA636@adacore.com>

Geert Bosch schrieb:
> On Sat, Apr 22, 2006 at 02:36:04PM +0200, Rene Scharfe wrote:
>> You can use "indent -npro -kr -i8 -ts8 -l80 -ss -ncs" to reformat your
>> code into a similar style as used in the rest of git (settings taken
>> from Lindent which is shipped with the Linux source).
> Although I cringe at 8-space indenting, and find much of the GIT
> code close to unreadable for lack of design-level comments, I'll
> gladly reformat any code to conform to existing code standards.
> Please let me know if you've got documentation on that, as it would
> be helpful for me to know what the standard is. (No flame intended. :-)

I'm not aware of a document mandating a certain formatting.  The output
of that indent call should come close to a "standard format", because
Linus followed this style from the beginning and Junio didn't go astray.

Don't worry too much about it.  I just wanted to point out an easy way
to reformat your code to use sane indenting. :->

René

  parent reply	other threads:[~2006-04-25 18:22 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-21 21:16 RFC: New diff-delta.c implementation Geert Bosch
2006-04-22  3:19 ` Nicolas Pitre
2006-04-22 11:04   ` Geert Bosch
2006-04-22 11:13     ` Junio C Hamano
2006-04-22 12:35       ` Geert Bosch
2006-04-22 12:51         ` Nicolas Pitre
2006-04-22 13:39           ` Geert Bosch
2006-04-22 17:03             ` Junio C Hamano
2006-04-22 17:28               ` Geert Bosch
2006-04-22 17:57                 ` Junio C Hamano
2006-04-22 12:45       ` Nicolas Pitre
2006-04-22 14:17         ` Geert Bosch
2006-04-22 17:29         ` Junio C Hamano
2006-04-22 19:58           ` Nicolas Pitre
2006-04-22  5:21 ` Davide Libenzi
2006-04-22  9:12   ` Geert Bosch
2006-04-22 12:36 ` Rene Scharfe
2006-04-24  2:57   ` Geert Bosch
2006-04-24  5:27     ` Nicolas Pitre
2006-04-24 15:19       ` Geert Bosch
2006-04-24 15:57         ` Nicolas Pitre
2006-04-24 16:31           ` Geert Bosch
2006-04-24 18:24             ` Geert Bosch
2006-04-24 18:27           ` Geert Bosch
2006-04-24 19:21           ` Rutger Nijlunsing
2006-04-24 20:37         ` Petr Baudis
2006-04-24 18:44       ` Geert Bosch
2006-04-25 18:22     ` Rene Scharfe [this message]
2006-04-22 20:36 ` Davide Libenzi
2006-04-23  2:31   ` Geert Bosch
2006-04-24 19:10     ` Davide Libenzi
2006-04-24 19:23       ` Geert Bosch

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=444E68DF.1020105@lsrfire.ath.cx \
    --to=rene.scharfe@lsrfire.ath.cx \
    --cc=bosch@adacore.com \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.