public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Martin Schlemmer <azarah@gentoo.org>
To: gentoo-dev@cvs.gentoo.org
Subject: Re: [gentoo-dev] Re: All Developers!
Date: Sat Nov 10 14:24:01 2001	[thread overview]
Message-ID: <1005427594.3250.10.camel@nosferatu.lan> (raw)
In-Reply-To: <20011110161447.A20091@yde.flatmonk.org>

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

On Sat, 2001-11-10 at 23:14, Aron Griffis wrote:
> Daniel Robbins wrote:	[Sat Nov 10 2001, 01:24:42PM EST]
> > 1) Use one tab per indent
> > 
> > 2) Put comments on separate lines
> > 
> > 3) Avoid using "/" line continuation characters and use long lines instead.
> 
> I don't care about 1 and 2, but I agree with Chouser about long lines.
> I don't mind terribly when I have to edit an existing ebuild with long
> lines, but *please* don't ask me to write them like that.
> 
> Continuations can make the code more understandable when used
> appropriately.  And it's easy to write continuations that don't have any
> problem with developers' tabbing preferences:
> 
> 	./configure \
> 		--prefix=/usr \
> 		--mandir=/usr/share/man \
> 		--infodir=/usr/share/info
> 
> This might be considered overuse of line continuations, but it makes my
> point; the code is readable, fits in a standard terminal, and has no
> issues with tabs.
> 
> Aron
> 

im ok with this, much better than one line, and solve the align problem
(although not as pretty ;-)


-- 

Martin Schlemmer
Gentoo Linux Developer, Desktop Team Developer
Cape Town, South Africa


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

      reply	other threads:[~2001-11-10 21:23 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
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 [this message]

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=1005427594.3250.10.camel@nosferatu.lan \
    --to=azarah@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