9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Jason Catena <jason.catena@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Acme Configuration
Date: Fri,  7 Aug 2009 13:50:19 -0500	[thread overview]
Message-ID: <d50d7d460908071150m72c7c4a1m54598fa041ad2206@mail.gmail.com> (raw)
In-Reply-To: <a81fe9be0908071023p3163581n571e5e391907288e@mail.gmail.com>

On Fri, Aug 7, 2009 at 12:23, yy<yiyu.jgl@gmail.com> wrote:
> 2009/8/7 roger peppe <rogpeppe@gmail.com>:
> Contents of all the taglines
>
> i have lost precious one-liners in column headers.

Didn't copy them into guide files in the current directory?  Seems to
work just as well for file commands, if not edit commands (which just
need copied back).

>> - Dump would dump to the restored-from file rather than
>> $home/acme.dump by default.

I put "Dump /where/ever/dumps/go" in the top tagline and highlight it,
works well enough for me.

> very good judgement is needed to accept or reject acme patches.

I can definitely attest to this principle in my own work.  In terms of
apprentice/journeyman/master for a particular program: the apprentices
write a lot of code, most of which is thrown away to get to a few good
ideas; the journeymen refine ideas into something worthy of a patch,
and may own a subsystem; and the master vets all code for
architectural coherence.  These roles vary by code base: I'm
apprentice of Plan 9, master of a 10-year-old build system.  I can
transfer some knowledge and skills, but still need to learn the
conventions and architecture before suggesting any dramatic (indeed,
noticeable) change.

Jason Catena



  reply	other threads:[~2009-08-07 18:50 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-08-07  8:37 Aaron W. Hsu
2009-08-07  9:20 ` Daniel Lyons
2009-08-07  9:39   ` erik quanstrom
2009-08-07 13:34   ` Jason Catena
2009-08-07 13:50     ` Noah Evans
2009-08-07 14:02       ` roger peppe
2009-08-07 14:28         ` Noah Evans
2009-08-07 15:42           ` roger peppe
2009-08-07 15:48             ` erik quanstrom
2009-08-07 16:05             ` ron minnich
2009-08-07 16:54             ` Noah Evans
2009-08-07 17:07               ` Iruata Souza
2009-08-07 17:16                 ` erik quanstrom
2009-08-07 17:23             ` yy
2009-08-07 18:50               ` Jason Catena [this message]
2009-08-07 19:00               ` yy
2009-08-08  4:16               ` 6o205zd02
2009-08-07 20:07 ` Uriel

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=d50d7d460908071150m72c7c4a1m54598fa041ad2206@mail.gmail.com \
    --to=jason.catena@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).