git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeff King <peff@peff.net>
To: Paul Wise <pabs3@bonedaddy.net>
Cc: git@vger.kernel.org
Subject: Re: interoperability between git and other VCS and data storage/transfer tools?
Date: Thu, 9 Jan 2020 02:57:48 -0500	[thread overview]
Message-ID: <20200109075748.GB3978837@coredump.intra.peff.net> (raw)
In-Reply-To: <929fe6f7f41a2abca353df4fd7f602a3e22ceb5f.camel@bonedaddy.net>

On Thu, Jan 09, 2020 at 08:59:51AM +0800, Paul Wise wrote:

> I still need mostly bi-directional interoperability between git and
> CVS, Subversion, Mercurial, Breezy/Bazaar, Darcs, Mediawiki and rsync.
> On the horizon are Fossil and Pijul but I probably won't need those any
> time soon. Recently I had a situation where GNU Arch support would have
> been helpful for viewing historical commit information but I assumed
> that support for it didn't exist so I didn't bother.

I don't know if you need it to be bidirectional, but there is
git-archimport. I'll warn you that it's pretty unmaintained, though so
best of luck. :)

> Is there a location in the git documentation for pointers to software
> (such as git-remote-* helpers) that can help with VCS interoperability?

There's:

  https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools#Interaction_with_other_Revision_Control_Systems

I have no idea how up-to-date it is (I admit that I converted all of my
repos to Git in 2006 and haven't really looked back).

> Mercurial: git-remote-hg (there are lots of forks/implementations)

I haven't used it, but there's also:

  https://github.com/glandium/git-cinnabar

which seems to be actively used and maintained.

-Peff

  reply	other threads:[~2020-01-09  7:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-09  0:59 interoperability between git and other VCS and data storage/transfer tools? Paul Wise
2020-01-09  7:57 ` Jeff King [this message]
2020-01-09  8:16   ` Paul Wise

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=20200109075748.GB3978837@coredump.intra.peff.net \
    --to=peff@peff.net \
    --cc=git@vger.kernel.org \
    --cc=pabs3@bonedaddy.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).