9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Charles Forsyth <forsyth@caldo.demon.co.uk>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Installed Plan 9, now what?
Date: Sun,  7 Dec 2003 09:59:32 +0000	[thread overview]
Message-ID: <c1b018929a358738a28c44acb478eda8@caldo.demon.co.uk> (raw)
In-Reply-To: <20031209041058.7427.qmail@g.galapagos.bx.psu.edu>

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

perhaps, but i think that's necessary anyway even with all the . this-and-that-local attempts,
and in some ways they make it less obvious that something has changed.
for instance, the main script might have changed the place the local part
is invoked, or its context (environment variables, name space etc),
thus changing the effect without giving you any warning.
if instead you simply change the original script, you can see what happens
in context, in one place, and applylog moans making it obvious that
you need to diff to consider the changes.

[-- Attachment #2: Type: message/rfc822, Size: 2338 bytes --]

From: Scott Schwartz <schwartz@bio.cse.psu.edu>
To: 9fans@cse.psu.edu
Subject: Re: [9fans] Installed Plan 9, now what?
Date: Mon, 08 Dec 2003 23:10:58 -0500
Message-ID: <20031209041058.7427.qmail@g.galapagos.bx.psu.edu>

| With the
| availability of dumps (or RCS on Lunix), there's little reason to be
| afraid of editing files.

The need to put things back isn't the problem; it's the need to notice
that something got stomped and the study required to integrate local
edits with the new reality.

  reply	other threads:[~2003-12-07  9:59 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-08 12:48 David Presotto
2003-12-08 15:10 ` andrey mirtchovski
2003-12-08 16:21   ` David Presotto
2003-12-08 19:30   ` Dan Cross
2003-12-08 21:14     ` david presotto
2003-12-08 22:20       ` Dan Cross
2003-12-09  0:55         ` David Presotto
2003-12-09  1:20           ` Russ Cox
2003-12-09  1:29             ` Dan Cross
2003-12-09  1:36               ` Russ Cox
2003-12-09  3:00                 ` Dan Cross
2003-12-09  4:02                   ` Geoff Collyer
2003-12-09  3:44                     ` mirtchov
2003-12-09  4:10                     ` Scott Schwartz
2003-12-07  9:59                       ` Charles Forsyth [this message]
2003-12-07 10:28                         ` Charles Forsyth
2003-12-09  4:33                       ` Geoff Collyer
2003-12-09  4:54                     ` Dan Cross
2003-12-09  7:47                       ` okamoto
2003-12-09 11:23                       ` a
2003-12-09 12:12                         ` boyd, rounin
2003-12-09 18:33                       ` splite
2003-12-09 19:23                         ` Brantley Coile
  -- strict thread matches above, loose matches on Subject: below --
2003-12-09  7:55 YAMANASHI Takeshi
2003-12-09 13:49 ` David Presotto
2003-12-08 11:36 Tiit Lankots
2003-12-08 14:51 ` ron minnich
2003-12-08 15:00 ` Russ Cox
2003-12-08 10:08 Sujan Gautam
2003-12-08 13:53 ` mirtchov

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=c1b018929a358738a28c44acb478eda8@caldo.demon.co.uk \
    --to=forsyth@caldo.demon.co.uk \
    --cc=9fans@cse.psu.edu \
    /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).