From: "Iruatã Souza" <iru.muzgo@gmail.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] hgfs?
Date: Thu, 26 May 2011 20:24:37 -0300 [thread overview]
Message-ID: <BANLkTinxKK_B4hFtuyh_5H=zz7s-uEOaSA@mail.gmail.com> (raw)
In-Reply-To: <20110526163958.02922B827@mail.bitblocks.com>
On Thu, May 26, 2011 at 1:39 PM, Bakul Shah <bakul@bitblocks.com> wrote:
>> 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.]
>
>
http://ueber.net/code/r/hgfs
next prev parent reply other threads:[~2011-05-26 23:24 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 ` [9fans] hgfs? Bakul Shah
2011-05-26 22:12 ` simon softnet
2011-05-26 23:24 ` Iruatã Souza [this message]
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='BANLkTinxKK_B4hFtuyh_5H=zz7s-uEOaSA@mail.gmail.com' \
--to=iru.muzgo@gmail.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).