9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Devon H. O'Dell" <devon.odell@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF
Date: Thu, 12 Apr 2007 12:08:17 -0400	[thread overview]
Message-ID: <9ab217670704120908s1407c1d1xbed0dcc2144b1ce7@mail.gmail.com> (raw)
In-Reply-To: <5d375e920704120856i3501d43aw6412b2b1ca0b48e3@mail.gmail.com>

2007/4/12, Uriel <uriel99@gmail.com>:
> On 4/12/07, Devon H. O'Dell <devon.odell@gmail.com> wrote:

[snip]

> > One thing I'm not sure of still is, if there is a cpurc.local, it may
> > want to implement some things dependent on e.g. what if you are
> > starting some client script that requires the network to already have
> > been initialized. This seems to be what you would end up putting in
> > your /cfg/$sysname/cpustart,
>
> We might want a /rc/bin/cpustart.local too?

No, it appears to serve the same purpose as cpurc.local --
cpu-specific startup, after initialization. (And it's not in the
default distribution). At what point do we stop and at what point do
we create cpustart.local.local.local?

> > We need to have something automatically create /cfg for peoples
> > fossils when they upgrade then. You can't just mkdir /cfg.
>
> Having /cfg by default might be a good idea, but I don't think it is a
> big deal as long as it is optional, I suspect most small networks can
> get by with cpurc.local and maybe a cpustart.local, and if you want
> /cfg, you can just create it and cpurc should take advantage of it
> automatically.

If we don't put /cfg in, I agree that cpustart.local is a good idea.

> > I could. How is your script splitting them up though? I was assuming
> > that it used those lines to split each change.
>
> For some unknown reason russ refused to have the changes split on his
> end, which would be the ideal. I have a script that splits the daily

Because it's a pain in the ass to go through all the changes individually.

> changes file and puts them in sources, see for example:
> /n/sources/contrib/uriel/changes/2007/0410/
> and then use that as input for the email notifications.
>
> If someone wants to get a single email per day, they can get a digest
> of plan9changes.
>
> To split I use some awk magic to detect text that is not indented,
> which is the comments that go over the diffs. See the end of
> /n/sources/contrib/uriel/plog for the (awful and fragile) details.

Ok. I'll start adding subjects then. But do please note, I'm not
intending to split them up past daily changelogs right now. Yes, the
makemail script does create separate changes, but editing them all
separately, figuring out what to name them, etc, would increase the
effort needed to do these things by a power of at least n*2.

--dho


  reply	other threads:[~2007-04-12 16:08 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <5247962e2f1f11c9b374c57d9a9a71db@cat-v.org>
2007-04-12 15:14 ` Uriel
2007-04-12 15:32   ` Devon H. O'Dell
2007-04-12 15:48     ` erik quanstrom
2007-04-12 16:03       ` Devon H. O'Dell
2007-04-12 16:05       ` Russ Cox
2007-04-12 15:56     ` Uriel
2007-04-12 16:08       ` Devon H. O'Dell [this message]
2007-04-12 17:42         ` [9fans] Re: [sources] 20070410: % cat geoff
2007-04-12 18:00           ` Anthony Sorace
2007-04-12 18:16             ` Russ Cox
2007-04-12 18:57               ` Anthony Sorace
2007-04-13  4:04           ` Lucio De Re
2007-04-13  4:58             ` geoff
2007-04-12 18:25       ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF ron minnich
2007-04-12 18:38         ` [9fans] Re: [sources] 20070410: % cat geoff
2007-04-12 18:43           ` Devon H. O'Dell
2007-04-12 18:40         ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF erik quanstrom
2007-04-12 18:50           ` Francisco J Ballesteros
2007-04-12 18:41         ` Russ Cox
2007-04-13  4:18           ` [9fans] Re: [sources] 20070410: % cat Lucio De Re
2007-04-13  4:59             ` geoff
2007-04-12 18:48         ` [9fans] Re: [sources] 20070410: % cat >/sys/lib/dist/changes/1176262206.1.txt << EOF 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=9ab217670704120908s1407c1d1xbed0dcc2144b1ce7@mail.gmail.com \
    --to=devon.odell@gmail.com \
    --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).