From mboxrd@z Thu Jan 1 00:00:00 1970 From: erik quanstrom Date: Thu, 22 May 2014 09:18:04 -0400 To: 9fans@9fans.net Message-ID: <3807097e00ba3d22d242a3fe3e365548@mikro.quanstro.net> In-Reply-To: <58840eae5583b958b552c36e597c30f6@proxima.alt.za> References: <58840eae5583b958b552c36e597c30f6@proxima.alt.za> MIME-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Subject: Re: [9fans] syscall 53 Topicbox-Message-UUID: ed2b704a-ead8-11e9-9d60-3106f5b1d025 > Is this the right place to discuss the actual procedure to include > apatch in one's private Bell Labs' distribution? > > Is it preferable to use apatch within 9atom, or is it reasonably > portable to the "legacy" (I presume that is what David intends > with that moniker) distribution? apatch is as specialized as patch in that it creates patches against the current 9atom tree. patch is still there, and i often generate parallel patches for both 9atom and sources. as long as your source hasn't drifted wrt the atom tree, you can send an apatch from a 9atom, hybride or standard tree. > Is there a willing participant who is prepared to offer backing > storage for the target distribution(s) even when he or she > disagrees with the outcome? (And be vociferous both about > disagreeing and accepting the outcome?) David, you've been good > that way, are there others? I'd like to think that we can > leverage Plan 9's distributable properties to have more than one? > I'd like to offer this myself, but I live at the bottom of an > Internet gravity well, anyone with sufficient patience is welcome > to approach me. you are aware that you can mount the 9atom sources directly these days? nflag=-n srv $nflag -q tcp!atom.9atom.org atom /n/atom atom # add to 9fs - erik