From: Theodore Tso <tytso@mit.edu>
To: Martin Langhoff <martin.langhoff@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Mozilla picks a DSCM system.... an amusing read
Date: Mon, 16 Apr 2007 06:26:58 -0400 [thread overview]
Message-ID: <20070416102658.GD27533@thunk.org> (raw)
In-Reply-To: <46a038f90704152127t43949a51h601e35cc4fc6aa7d@mail.gmail.com>
On Mon, Apr 16, 2007 at 04:27:51PM +1200, Martin Langhoff wrote:
> On 4/16/07, Martin Langhoff <martin.langhoff@gmail.com> wrote:
> >From a git POV, this is only the 2nd-best scenario -- once they are on
> >hg, the barriers of migration to git are much lower.
>
> Specially if we write git-hgserver sometime soon ;-)
Yeah, if I could clone myself or otherwise get a few weeks of
uninterrupted hacking time, I'd be writing a bidrectional hg<->git
gateway.... it's the main reason at this point why I haven't switched
e2fsprogs to git.
- Ted
prev parent reply other threads:[~2007-04-16 10:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-15 21:34 Mozilla picks a DSCM system.... an amusing read Theodore Ts'o
2007-04-16 4:15 ` Shawn O. Pearce
2007-04-16 7:15 ` Alex Riesen
2007-04-16 4:26 ` Martin Langhoff
2007-04-16 4:27 ` Martin Langhoff
2007-04-16 10:26 ` Theodore Tso [this message]
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=20070416102658.GD27533@thunk.org \
--to=tytso@mit.edu \
--cc=git@vger.kernel.org \
--cc=martin.langhoff@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).