9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: ori@eigenstate.org
To: 9fans@hamnavoe.com, 9fans@9fans.net
Subject: Re: [9fans] upgrading the 9legacy shell (was: Gmail vs Upas)
Date: Tue, 3 Dec 2019 09:43:50 -0800	[thread overview]
Message-ID: <380394A347CDB4C8B684FFCBC5DE0281@eigenstate.org> (raw)
In-Reply-To: <52366c2a6ccc545fc29dbabbf82b5a6c@hamnavoe.com>

>> and nobody is building a
>> release with an "OFFICIAL" stamp on it
> 
> What exactly would you want such a stamp to mean?
> 

Largely 2 things:

	1) That this is the "up to date plan 9" that the
	   community around it believes should be used.

	   This seems to have improved since the last
	   time I looked -- 9legacy.org no longer calls
	   itself 'an experimental patch queue'. Good!

	2) That the update mechanisms documented will
	   bring you up to date and incorporate those
	   changes. It seems that the documented way
	   to update your system is still replica/pull.
	   I haven't checked that it still works.


      parent reply	other threads:[~2019-12-03 17:43 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-03  4:10 Lucio De Re
2019-12-03  6:17 ` ori
2019-12-03 10:19   ` Richard Miller
2019-12-03 11:42     ` Lucio De Re
2019-12-03 15:25       ` hiro
2019-12-03 20:01         ` Skip Tavakkolian
2019-12-03 20:31           ` hiro
2019-12-03 22:06             ` Skip Tavakkolian
2019-12-03 22:46               ` hiro
2019-12-03 22:53                 ` andrey mirtchovski
2019-12-04  0:46                 ` Skip Tavakkolian
2019-12-04  1:06                 ` sstallion
2019-12-04  1:18                   ` Alex Musolino
2019-12-04  4:55                     ` Lucio De Re
2019-12-04  5:28                       ` Alex Musolino
2019-12-04 14:59                   ` hiro
2019-12-04 16:42                     ` Nicolas S. Montanaro
2019-12-03 17:43     ` ori [this message]

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=380394A347CDB4C8B684FFCBC5DE0281@eigenstate.org \
    --to=ori@eigenstate.org \
    --cc=9fans@9fans.net \
    --cc=9fans@hamnavoe.com \
    /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).