public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Luke-Jr <luke-jr@gentoo.org>
To: "Jason A. Mobarak" <aether@gentoo.org>, gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] Some 'proper coding' notes for ebuilds
Date: Sun, 3 Aug 2003 06:11:31 +0000	[thread overview]
Message-ID: <200308030611.42336.luke-jr@gentoo.org> (raw)
In-Reply-To: <3F2C9E3E.3070005@gentoo.org>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Unless I'm mistaken, most of this is in some document on the website 
already...

On Sunday 03 August 2003 05:31 am, Jason A. Mobarak wrote:
> Mike Frysinger wrote:
> > On Saturday 02 August 2003 22:29, Mike Frysinger wrote:
> >>just a few notes ...
> >>(1) checking $DEBUG and $DEBUGBUILD is wrong ... utilize `use debug`
> >>(2) do not use spaces for indenting ... tabs are the standard
> >>lub & kisses
> >>-mike
> >
> > oh, and instead of using $DEBUG and printing out debug related
> > information, use the debug-* functions ... see kde.eclass for some *very*
> > good examples of how to properly use them
> > -mike
>
> Hey Mike, perhaps you should finalize all these coding standards into a
> document so you can refer people to it.

- -- 
Luke-Jr
Developer, Gentoo Linux
http://www.gentoo.org/
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (GNU/Linux)

iD8DBQE/LKeaZl/BHdU+lYMRAlS7AJ9hmpNOwgpxdAwlCPlXpy7qsNusegCfY6RN
Xh3IoJkVVccNIqZyFKIFOes=
=Uuvi
-----END PGP SIGNATURE-----


--
gentoo-dev@gentoo.org mailing list


  parent reply	other threads:[~2003-08-03  6:11 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-08-03  2:29 [gentoo-dev] Some 'proper coding' notes for ebuilds Mike Frysinger
2003-08-03  2:34 ` Mike Frysinger
2003-08-03  2:38   ` Mike Frysinger
2003-08-03  2:50     ` Kumba
2003-08-03  3:04       ` Mike Frysinger
2003-08-03 15:23         ` Martin Schlemmer
2003-08-03 18:44           ` Mike Frysinger
2003-08-03 15:10     ` Mamoru KOMACHI
2003-08-03 15:40       ` Paul de Vrieze
2003-08-03 16:23         ` Mamoru KOMACHI
2003-08-03 16:27       ` Georgi Georgiev
2003-08-03 17:04         ` Mamoru KOMACHI
2003-08-03 15:30     ` Martin Schlemmer
2003-08-11 13:45     ` Patrick Kursawe
2003-08-11 14:58       ` Mike Frysinger
2003-08-03  5:31   ` Jason A. Mobarak
2003-08-03  4:56     ` Mike Frysinger
2003-08-03  6:11     ` Luke-Jr [this message]
2003-08-03 14:55   ` Stuart Herbert
2003-08-03 15:18     ` Martin Schlemmer
2003-08-03 18:07       ` Stuart Herbert
2003-08-03 18:48         ` Mike Frysinger
2003-08-03 18:53           ` Stuart Herbert
2003-08-03 20:27             ` George Shapovalov
2003-08-03 20:34               ` Stuart Herbert
2003-08-03 22:15                 ` George Shapovalov
2003-08-03 22:56                   ` Don Seiler
2003-08-08 15:21                     ` Anthony de Boer
2003-08-08 15:33                       ` Marius Mauch
2003-08-08 18:25                       ` George Shapovalov
2003-08-08 19:16                         ` Douglas Russell
2003-08-08 20:12                           ` George Shapovalov
2003-08-08 23:01                             ` Mike Frysinger
2003-08-10  2:58                             ` George Shapovalov
2003-08-03 22:19                 ` Aron Griffis
     [not found]             ` <20030803223541.05d10e90.spider@gentoo.org>
2003-08-03 20:43               ` Stuart Herbert

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=200308030611.42336.luke-jr@gentoo.org \
    --to=luke-jr@gentoo.org \
    --cc=aether@gentoo.org \
    --cc=gentoo-dev@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