9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: dante <subscriptions@posteo.eu>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] Plan9 Sources Repository
Date: Sat, 19 Jul 2014 11:31:56 +0200	[thread overview]
Message-ID: <1fc1c403eaecd8cae89f761a68b0d605@posteo.de> (raw)
In-Reply-To: <ae477372785e7286eba615da14d70a1e@ladd.quanstro.net>

I would like first to thank everyone for the kind replies!
Each was useful in it's own way.

On 18.07.2014 16:36, erik quanstrom wrote:
>> Yet: is there a source control system behind it?
>> Would it be possible to check out directly from there?
>
> there is nothing most folks would recognize as a distributed
> revision control system.
>
> the repo is sources itself.  history is through history(1).
> you can "check out" code with cp(1), tar(1), mkfs(8); you can
> keep up with the repo with replica(1).
>
> patches are submitted via patch(1).

I would argument that the Status Quo has the following disadvantages
when compared to the the current usual way of doing things:

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

2. There are no commit comments.
     There is no "blame" command.
     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...

3. Contrib packages are tied to people; there is no common repository.
     This leads to the situation where you can't update a package of a
long gone user.
     Please tell me how many Mercurial packages you can find in Contrib!

I maintain my impression that the Status Quo, though good for a small
team, does not allow the project to grow.
Were there any efforts to change this?
Or is it a controversial matter and it stays as it is?
Or is the team indeed so small (or even loosing members), s.t. that a
change won't make sense?

Kind Regards,
Dante

>
>> If there is none, could it be that this contributes to the lack of
>> popularity and to the fragmentation of Plan9 (9front, 9atom, 9legacy,
>> PlanB, other plans...)?
>
> i would think the "lack of popularity" can be most directly attributed
> to the closed license in the early 90s, when there was an unfilled
> niche,
> and linux was seriously lacking.
>
> i starting doing something slightly different when il was pulled from
> the distribution while i was in no position to stop using it.  it had
> nothing
> to do with source control.
>
> - erik



  reply	other threads:[~2014-07-19  9:31 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 [this message]
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
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=1fc1c403eaecd8cae89f761a68b0d605@posteo.de \
    --to=subscriptions@posteo.eu \
    --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).