9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jeremy Jackins <jeremyjackins@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan 9/plan9port coding conventions
Date: Wed, 11 Jan 2012 12:01:33 -0700	[thread overview]
Message-ID: <CAOr72mjYR-b481vU1e_stsVqSQeoajixcKi6EhJxyAh7Pje-Pg@mail.gmail.com> (raw)
In-Reply-To: <86vcoif5f4.fsf@cmarib.ramside>

> Are these practices official/unofficial Plan 9 coding conventions?  Are
> they used for performance purposes?  Are they just poor style?  Or has
> this kind of style been used for so long that it's BECOME Plan 9's style
> of choice?  Also, is it considered polite or acceptable coding practice
> to alter the style of code written by other contributors?  I don't want
> to step on anybody's toes by "fixing" style which other Plan 9
> developers consider to be "Plan 9" style coding conventions.

I'm not an active community member, but it seems you are confusing
style different from your own with poor style.



  parent reply	other threads:[~2012-01-11 19:01 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-01-11 18:41 smiley
2012-01-11 18:53 ` Richard Miller
2012-01-12 20:20   ` Yaroslav
2012-01-11 19:01 ` Jeremy Jackins [this message]
2012-01-11 20:37 ` Russ Cox
2012-01-11 20:45 ` erik quanstrom
2012-01-11 21:20 ` John Floren
2012-01-11 21:25   ` Russ Cox
2012-01-11 23:00   ` Iruatã Souza
2012-01-11 23:57     ` John Stalker
2012-01-12  1:33       ` Skip Tavakkolian
     [not found]       ` <CAJSxfmJdLV8NMJgMFPcqCP+=ZGe8k2U=PcdkpexwUzbcL442+Q@mail.gmail.c>
2012-01-12  2:53         ` erik quanstrom
2012-01-12 15:18 ` Comeau At9Fans
2012-01-12 17:56 ` Christian Neukirchen
2012-01-12 23:07   ` Skip Tavakkolian
2012-01-13 14:55 ` Andrés Domínguez
2012-01-16 10:02 ` faif
2012-01-16 11:04   ` John Stalker
2012-01-16 22:50 ` smiley
2012-01-16 22:57   ` andrey mirtchovski

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=CAOr72mjYR-b481vU1e_stsVqSQeoajixcKi6EhJxyAh7Pje-Pg@mail.gmail.com \
    --to=jeremyjackins@gmail.com \
    --cc=9fans@9fans.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 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).