9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] Plan9 Sources Repository
Date: Sat, 19 Jul 2014 10:41:57 -0400	[thread overview]
Message-ID: <bc6b9ca42ba0156f2f4d9200517e009e@ladd.quanstro.net> (raw)
In-Reply-To: <1fc1c403eaecd8cae89f761a68b0d605@posteo.de>

> 1. The history is confined to Plan9.
>      It is hard to do small fixes (typos, documentation) from another
> system.

that's true.  but it's easy to get a plan 9 system, or drawterm into one.
in my experience, plan 9 is a system one spends siginficant time in.

i would not want to change the system to support foreign patches unless
it's a proven issue, and experiments show that such patches are of equal
quailty to ones made from a plan 9 system.

solutions like hg pull python into the system as a hard requirement, and
i wouldn't want to make (more) external things like python a hard
requirement, if possible.  also, python doesn't currently work on
arm or mips, so it would making the minimum requirements for a plan 9
system much greater.

> 2. There are no commit comments.
>      There is no "blame" command.

but there is!  history(1) will display the last modifier of the file.
in plan 9 the rule typically is: you touch it, you own it.

>      There are no release tags (allowing for unstable work in between).
>      There are no branches (allowing for collective work on an unstable
> version). OK, my machine is my branch...

it's just a different model.

given your questions, i am wondering if you have spent much time with
the system.  especially one with history enabled.

- erik



  parent reply	other threads:[~2014-07-19 14:41 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-07-18 13:19 dante
2014-07-18 14:14 ` Aram Hăvărneanu
2014-07-18 14:18 ` cam
2014-07-18 14:36 ` erik quanstrom
2014-07-19  9:31   ` dante
2014-07-19 11:20     ` Riddler
2014-07-19 11:50       ` dante
2014-07-19 11:49     ` pmarin
2014-07-19 11:51       ` dante
2014-07-19 12:02         ` dante
2014-07-19 19:06           ` Anthony Sorace
2014-07-20  0:12           ` Brian L. Stuart
2014-07-20  7:33             ` dante
2014-07-19 12:03       ` tlaronde
2014-07-19 12:12         ` dante
2014-07-19 14:41     ` erik quanstrom [this message]
2014-07-19 15:06       ` dante
2014-07-19 15:11         ` Jacob Todd
2014-07-19 15:49           ` dante
2014-07-19 18:00             ` Kurt H Maier
2014-07-19 23:19               ` Brian L. Stuart
2014-07-19 18:17             ` erik quanstrom
2014-07-19 19:20               ` Christopher Nielsen
2014-07-19 20:13                 ` Aram Hăvărneanu
2014-07-19 22:10               ` dante
2014-07-19 22:30                 ` erik quanstrom
2014-07-20  7:33                   ` dante
2014-07-19 22:54                 ` Brian L. Stuart
2014-07-19 17:31         ` hiro
2014-07-19 17:48           ` dante
2014-07-19 15:03     ` Aram Hăvărneanu

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=bc6b9ca42ba0156f2f4d9200517e009e@ladd.quanstro.net \
    --to=quanstro@quanstro.net \
    --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).