From: dexen.devries@gmail.com (dexen deVries)
Subject: [9fans] drawterm bug
Date: Fri, 25 Mar 2011 21:09:17 +0100 [thread overview]
Message-ID: <201103252109.18156.dexen.devries@gmail.com> (raw)
In-Reply-To: <1301082530.30065.1433892565@webmail.messagingengine.com>
On Friday 25 of March 2011 20:48:50 Ethan Grammatikidis wrote:
> What on Earth is a quilted patch queue? I always thought the whole point
> of using a drcs was that you could work in your own branch. I've only
> used a drcs once, but everyone had their own branch there & it went
> pretty smoothly.
I believe branches in hg are somewhat permanent. Your branches have direct,
one-to-one, relationship with remote ones. Also, you can't exactly remove a
branch in it, AFAIK. But there is `Local Branch Extension' available.
after using hg for some time, i went for git where branches are more
ephemeral. no idea why this group shuns git, but i'm in no position to
proselytise.
perhaps porting fossil (the dvcs) [1] to plan 9 would be a good option?
[1] an unfortunate name conflict -- aside of the fossil archival filesystem
there is fossil DVCS (by the sqlite guys), implemented in C (probably c99
flavor)
http://en.wikipedia.org/wiki/Fossil_(software)
--
dexen deVries
``One can't proceed from the informal to the formal by formal means.''
next prev parent reply other threads:[~2011-03-25 20:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-21 15:36 erik quanstrom
2011-03-22 14:40 ` erik quanstrom
2011-03-22 17:40 ` erik quanstrom
2011-03-22 17:59 ` Skip Tavakkolian
2011-03-22 18:57 ` erik quanstrom
2011-03-22 17:45 ` Jeff Sickel
2011-03-22 17:51 ` erik quanstrom
2011-03-22 18:02 ` Jeff Sickel
2011-03-25 19:48 ` Ethan Grammatikidis
2011-03-25 20:09 ` dexen deVries [this message]
2011-03-25 21:00 ` Jeff Sickel
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=201103252109.18156.dexen.devries@gmail.com \
--to=dexen.devries@gmail.com \
/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).