From: Bakul Shah <bakul@bitblocks.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] hgfs
Date: Thu, 22 May 2014 12:46:42 -0700 [thread overview]
Message-ID: <20140522194642.8709EB82A@mail.bitblocks.com> (raw)
In-Reply-To: Your message of "Thu, 22 May 2014 12:41:05 +0200." <CAEAzY39-Q_j0uo5qRVL2E-O8mYVtzr2R-GTGOU-xfx5C=xoG1A@mail.gmail.com>
On Thu, 22 May 2014 12:41:05 +0200 =?UTF-8?B?QXJhbSBIxIN2xINybmVhbnU=?= <aram.h@mgk.ro> wrote:
>
> What would be the point of this? Once you have a version (revision)
> you can just bind the subtree where you want it. I don't see the
> point in having this special switching code inside hgfs. Plan 9
> provides the necessary functionality.
I agree on this specific point.
If I am working on branch A and I want to switch to B, git
forces me to commit or "stash" my changes. So even after
gadzillion lines of code it still doesn't do the right thing.
A tool should not force singlethreading on me. And hg is no
better in this regard. This limitation need not exist on
plan9.
next prev parent reply other threads:[~2014-05-22 19:46 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-22 6:52 Skip Tavakkolian
2014-05-22 7:36 ` lucio
2014-05-22 9:54 ` Aram Hăvărneanu
2014-05-22 10:30 ` lucio
2014-05-22 10:41 ` Aram Hăvărneanu
2014-05-22 15:35 ` Skip Tavakkolian
2014-05-22 15:56 ` erik quanstrom
2014-05-22 16:17 ` ron minnich
2014-05-22 16:21 ` Kurt H Maier
2014-05-22 16:31 ` Aram Hăvărneanu
2014-05-22 18:37 ` ron minnich
2014-05-22 18:45 ` Kurt H Maier
2014-05-22 18:51 ` Aram Hăvărneanu
2014-05-22 19:02 ` Latchesar Ionkov
2014-05-22 19:13 ` Kurt H Maier
2014-05-22 19:16 ` erik quanstrom
2014-05-22 19:23 ` Latchesar Ionkov
2014-05-23 3:45 ` hiro
2014-05-22 19:11 ` Skip Tavakkolian
2014-05-22 19:23 ` Bakul Shah
2014-05-22 19:47 ` Skip Tavakkolian
2014-05-22 16:20 ` lucio
2014-05-22 19:46 ` Bakul Shah [this message]
-- strict thread matches above, loose matches on Subject: below --
2011-06-27 5:43 cinap_lenrek
2011-06-27 13:15 ` hiro
2011-06-27 5:09 cinap_lenrek
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=20140522194642.8709EB82A@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).