From: erik quanstrom <quanstro@quanstro.net>
To: 9fans@9fans.net
Subject: Re: [9fans] revision control system or SCM of Plan 9 sources
Date: Mon, 12 Apr 2010 08:23:40 -0400 [thread overview]
Message-ID: <533812b16ec5399143186938e30cd7a3@kw.quanstro.net> (raw)
In-Reply-To: <d188ce55-27fd-4cb0-a984-791f857b21da@q15g2000yqj.googlegroups.co>
On Mon Apr 12 05:32:39 EDT 2010, boobsd@gmail.com wrote:
> Hi folks,
> Is there any revision control system or SCM of Plan 9 sources? I would
> like to read changesets, but don't know where I can find them.
> Thanks.
not really. if you want to read revision history, you
can use history(1) on sources. unfortunately this requires
a sources account.
- erik
next parent reply other threads:[~2010-04-12 12:23 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <d188ce55-27fd-4cb0-a984-791f857b21da@q15g2000yqj.googlegroups.co>
2010-04-12 12:23 ` erik quanstrom [this message]
2010-04-12 9:30 Boo
2010-04-12 13:44 ` Gabriel Díaz
2010-04-12 14:29 ` Nathaniel W Filardo
2010-04-12 14:58 ` Boo
2010-04-13 15:43 ` maht
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=533812b16ec5399143186938e30cd7a3@kw.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).