From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: [9fans] hgfs?
Date: Thu, 26 May 2011 09:39:57 -0700 [thread overview]
Message-ID: <20110526163958.02922B827@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Thu, 26 May 2011 10:26:08 EDT." <BANLkTikvqeKg-MB431qJi=NZZjr-fkpPTA@mail.gmail.com>
> Typically the way to do this is to create your own public fork, and
> then send a pull request to the maintainer of whoever you forked from
> since hg has the distributed model.
A project idea: murkyfs -- browse not just your own mercurial
repo and also the one you cloned from! Extra points for
mapping hg commands like push/pull/merge/diff in a useful way.
Another idea is a better integration of acem + hg. [One side
effect using Eclipse is I have been thinking about how one
might build a simple IDE around acme or something similar.]
next prev parent reply other threads:[~2011-05-26 16:39 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 3:27 [9fans] 9vx bootimage build instructions? EBo
2011-05-26 3:37 ` erik quanstrom
2011-05-26 3:58 ` EBo
2011-05-26 4:05 ` EBo
2011-05-26 4:18 ` Devon H. O'Dell
2011-05-26 4:24 ` Bakul Shah
2011-05-26 7:40 ` yy
2011-05-26 14:06 ` [9fans] 9vx patches [was: 9vx bootimage build instructions?] EBo
2011-05-26 14:26 ` Devon H. O'Dell
2011-05-26 16:39 ` Bakul Shah [this message]
2011-05-26 22:12 ` [9fans] hgfs? simon softnet
2011-05-26 23:24 ` Iruatã Souza
2011-05-27 0:16 ` erik quanstrom
2011-05-27 8:12 ` Bakul Shah
2011-05-27 12:21 ` erik quanstrom
2011-05-27 14:45 ` Lucio De Re
2011-05-27 17:18 ` Bakul Shah
2011-05-27 17:30 ` erik quanstrom
2011-05-26 15:34 ` [9fans] 9vx patches [was: 9vx bootimage build instructions?] erik quanstrom
2011-05-26 18:17 ` EBo
2011-05-26 18:58 ` erik quanstrom
2011-05-26 19:17 ` EBo
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=20110526163958.02922B827@mail.bitblocks.com \
--to=bakul@bitblocks.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).