9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: "Anthony Sorace" <anothy@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Applying patches to local machine
Date: Fri,  2 Nov 2007 06:39:18 -0400	[thread overview]
Message-ID: <509071940711020339n68ef9648vb5970a02ab86703b@mail.gmail.com> (raw)
In-Reply-To: <f1cb3ec7f86c5332a61917059a49a37f@terzarima.net>

I think he's asking whether there's any way to apply not yet
integrated/approved patches to his local source.

It looks like running patch/apply works for everyone, modifying
whatever the local root is (rather than explicitly working on
/n/sources), which is nice. It does require you having write
permissions on (its view of) the patch directory itself:

	:; patch/apply savec/cpu-cec
	.tmp: rc (apply): can't open: '.tmp' permission denied
	:; ramfs && bind -bc /tmp /n/sources/patch/saved/cpu-cec
	:; patch/apply saved/cpu-cec
	merge...backup...cp: can't stat /sys/src/9/port/devcec.c:
'/sys/src/9/port/devcec.c' does not exist
copy...
	to update sources:
		update /sys/src/9/port/portfns.h
		update /sys/src/9/port/devcec.c
		update /sys/src/9/port/devcons.c

That cp error after backup is just because devcec.c isn't an existing
file in the system. I'm not sure whether those update lines are
intended to be executable commands we just don't have (looks like) or
advisory, but either way your local tree is now updated.

This is neat, by the way. I'd never thought to actually check if this
worked or not. Given it's this easy, I think I'll play around with the
rio pie menu stuff. Thanks!

Anthony


  parent reply	other threads:[~2007-11-02 10:39 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-02 10:11 Christian Kellermann
2007-11-02 10:21 ` Charles Forsyth
2007-11-02 10:25   ` Christian Kellermann
2007-11-02 10:39   ` Anthony Sorace [this message]
2007-11-02 10:44     ` Christian Kellermann
2007-11-02 11:35       ` Christian Kellermann
2007-11-02 11:52         ` Anthony Sorace
2007-11-02 12:35           ` erik quanstrom
2007-11-02 18:47           ` Dave Eckhardt

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=509071940711020339n68ef9648vb5970a02ab86703b@mail.gmail.com \
    --to=anothy@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).