From: Paul Wise <pabs3@bonedaddy.net>
To: git@vger.kernel.org
Subject: interoperability between git and other VCS and data storage/transfer tools?
Date: Thu, 09 Jan 2020 08:59:51 +0800 [thread overview]
Message-ID: <929fe6f7f41a2abca353df4fd7f602a3e22ceb5f.camel@bonedaddy.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 1718 bytes --]
Hi all,
[Please CC me in reply, I am not subscribed]
I would like to be only using git on my local systems but there are
other folks out there who prefer to use different VCS systems.
In addition there are VCS-like data storage systems (such as Mediawiki)
and general data storage/transfer systems where one might want to track
changes using git (such as LDAP and rsync).
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.
Is there a location in the git documentation for pointers to software
(such as git-remote-* helpers) that can help with VCS interoperability?
Is there a place for people interested in VCS interoperability software
to collaboratively maintain them?
Should the VCS interop software in the git git repo move there?
I'm currently using the following tools:
CVS: https://github.com/osamuaoki/git-cvs (slightly better than git-cvsimport)
Subversion: git-svn (not using a git-remote-* workflow)
Mercurial: git-remote-hg (there are lots of forks/implementations)
Breezy/Bazaar: git-remote-bzr (there are lots of forks)
Darcs: nothing as only fast-export/fast-import seems possible
Mediawiki: https://github.com/Git-Mediawiki/Git-Mediawiki
rsync: manually rsyncing and importing commits
What other tools are folks using?
Any other thoughts on this?
--
bye,
pabs
https://bonedaddy.net/pabs3/
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next reply other threads:[~2020-01-09 1:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-09 0:59 Paul Wise [this message]
2020-01-09 7:57 ` interoperability between git and other VCS and data storage/transfer tools? Jeff King
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=929fe6f7f41a2abca353df4fd7f602a3e22ceb5f.camel@bonedaddy.net \
--to=pabs3@bonedaddy.net \
--cc=git@vger.kernel.org \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).