public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Mikael Hallendal <hallski@gentoo.org>
To: "Gentoo Dev." <gentoo-dev@cvs.gentoo.org>
Subject: Re: [gentoo-dev] Re: All Developers!
Date: Sun Nov 11 06:27:01 2001	[thread overview]
Message-ID: <1005481622.24118.0.camel@fry> (raw)
In-Reply-To: <20011110140446.F16660@cvs.gentoo.org>

[-- Attachment #1: Type: text/plain, Size: 1244 bytes --]

lör 2001-11-10 klockan 22.04 skrev Daniel Robbins:
> On Sat, Nov 10, 2001 at 03:39:13PM -0500, Chris Houser wrote:
> > Daniel Robbins wrote:                 [Sat Nov 10 2001,  1:24:42PM EST]         
> > > OK, if people need rules, I can provide them:
> > > 
> > > 1) Use one tab per indent
> > > 
> > > 2) Put comments on separate lines
> > > 
> > > 3) Avoid using "/" line continuation characters and use long lines instead.
> > 
> > Oh, please not 3) ... I realy dislike long lines.  I don't think it's
> > too big a deal if the line continuations don't line up for everybody.
> 
> OK, I'll amend 3.  Either you can use long lines, or you can use "/" line
> continuation characters.  If you *do* use line continuation characters, you
> should *not* try to tab align them so that they're "pretty".  Instead, follow
> the line with a single space, then a "/", and then a newline.

Hmm .. imho it's much easier to read with the \ aligned.
I think we can do this by supplying a emacs/vi-mode for editing ebuilds.
Those modes should be strict and force the developer to do it right.

Regards,
  Mikael Hallendal

-- 

Mikael Hallendal
Gentoo Linux Developer, Desktop Team Leader
CodeFactory AB, Stockholm, Sweden


[-- Attachment #2: Type: application/pgp-signature, Size: 232 bytes --]

  parent reply	other threads:[~2001-11-11 13:26 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-11-10  4:35 [gentoo-dev] All Developers! Mikael Hallendal
2001-11-10  5:22 ` Martin Schlemmer
2001-11-10  6:00   ` [gentoo-dev] " Andreas Voegele
2001-11-10  6:12     ` Mikael Hallendal
2001-11-10  6:17     ` Martin Schlemmer
2001-11-10  7:58 ` [gentoo-dev] " Karl Trygve Kalleberg
2001-11-10  8:37   ` Mikael Hallendal
2001-11-10  9:05     ` [gentoo-dev] " Andreas Voegele
2001-11-10  9:29       ` Martin Schlemmer
2001-11-10  9:38       ` Chad Huneycutt
2001-11-10 11:25         ` Daniel Robbins
2001-11-10 13:42           ` Chris Houser
2001-11-10 14:05             ` Daniel Robbins
2001-11-10 14:23               ` Aron Griffis
2001-11-11  6:27               ` Mikael Hallendal [this message]
2001-11-11  6:35                 ` Martin Schlemmer
2001-11-11  6:41                   ` Mikael Hallendal
2001-11-21 19:16                   ` Damon M. Conway
2001-11-21 20:08                     ` Daniel Robbins
2001-11-11 10:06                 ` Andreas Voegele
2001-11-11 12:09                   ` jano
2001-11-11 14:17                     ` Mikael Hallendal
2001-11-11 15:26                   ` Tom von Schwerdtner
2001-11-10 14:17           ` Aron Griffis
2001-11-10 14:24             ` Martin Schlemmer

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=1005481622.24118.0.camel@fry \
    --to=hallski@gentoo.org \
    --cc=gentoo-dev@cvs.gentoo.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