From mboxrd@z Thu Jan 1 00:00:00 1970 Message-ID: <509071940711020339n68ef9648vb5970a02ab86703b@mail.gmail.com> Date: Fri, 2 Nov 2007 06:39:18 -0400 From: "Anthony Sorace" To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu> Subject: Re: [9fans] Applying patches to local machine In-Reply-To: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit Content-Disposition: inline References: <20071102101123.GB18785@hermes.my.domain> Topicbox-Message-UUID: e5e88d32-ead2-11e9-9d60-3106f5b1d025 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