9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: Skip Tavakkolian <skip.tavakkolian@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Update APE
Date: Tue, 21 Feb 2017 02:59:27 +0000	[thread overview]
Message-ID: <CAJSxfmJCoK22PLCoKTaGoEtCfgwvekqpbhEf9qg48z61NeaHjg@mail.gmail.com> (raw)
In-Reply-To: <a90332a540bd5a3e34bf2298e67a47c2@quintile.net>

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

David du Colombier has kept up a comprehensive list of patches at 9legacy (
https://www.9legacy.org/patch.html); it's the best place to start.

Although patches can still be submitted to Labs' sources, the last time any
kernels in that repository were updated was in 2014. Fortunately there are
other maintained distributions[*]
I'm not sure how patches made in one distribution make their way into other
distributions.

I don't know how long this form of patches against Labs' frozen version
would be possible.  As patches pile on, a set of deltas need to be kept
going back to the Labs' sources.  It begs the question of how do we
organize a community maintained repository?

[*] list of Plan 9 distro's I'm aware of:
9legacy distro: maintained by David du Colombier
9front distro: kept up by ɔᴉuɐd lǝuɹǝʞ and 9 people's front people
9atom distro: kept up by Erik Quanstrom
9pi (bcm) kernel: maintained by Richard Miller; sources are in contrib area
on Labs' sources



On Mon, Feb 20, 2017 at 4:47 PM Steve Simon <steve@quintile.net> wrote:

> sadly there doesn't seem to be a way to add users to the labs sources
> server,
> unless somone knows different.
>
> I think the best thing would be to post diffs to this mailing list.
>
> I have some small changes to APE I have been meaning to post, nothing
> substantial
> mut enough to make porting some tools easier.
>
> -Steve
>
>

[-- Attachment #2: Type: text/html, Size: 2360 bytes --]

  reply	other threads:[~2017-02-21  2:59 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-20 18:48 Charlie Lin
2017-02-20 19:49 ` Jens Staal
2017-02-21 22:20   ` cigar562hfsp952fans
2017-02-21 23:55     ` Jadon Bennett
2017-02-22  5:48     ` Jens Staal
2017-02-22 17:27     ` Dave MacFarlane
2017-02-22 18:23       ` Skip Tavakkolian
2017-02-24 16:24         ` michaelian ennis
2017-02-21  0:02 ` Steve Simon
2017-02-21  2:59   ` Skip Tavakkolian [this message]
2017-02-21  3:39     ` Lyndon Nerenberg
2017-02-21  4:09       ` Skip Tavakkolian
2017-02-21  4:12     ` Kurt H Maier
2017-02-21  8:38       ` Charles Forsyth
2017-02-21 16:24         ` Kurt H Maier

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=CAJSxfmJCoK22PLCoKTaGoEtCfgwvekqpbhEf9qg48z61NeaHjg@mail.gmail.com \
    --to=skip.tavakkolian@gmail.com \
    --cc=9fans@9fans.net \
    /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).