From: Tim Chase <git@tim.thechases.com>
To: git@vger.kernel.org
Subject: Git -> fossil bridging?
Date: Sun, 17 Nov 2013 15:00:10 -0600 [thread overview]
Message-ID: <20131117150010.675971d3@bigbox.christie.dr> (raw)
Has there been any development on git<->fossil bridging? I know one
can spew fastimports between the two for an initial synchronization,
but I'd like to have a continuous bridge; something like git-svn.
I have fossil on one machine (mostly a public machine, for
bug-tracking, wiki, etc that fossil does nicely) while using git
locally and pushing change-sets out to the fossil repo.
Any tips?
My current experimentation just houses both in the same location with
my git "master" branch manually synced with the fossil repo (which is
really all I need which does simplify matters greatly, though it
would be nice to sync multiple branches if the functionality was
there).
Thanks,
-tkc
next reply other threads:[~2013-11-17 22:03 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 21:00 Tim Chase [this message]
[not found] ` <575D57DB-026F-484E-8068-E7965395E902@gmail.com>
2013-11-18 0:26 ` Git -> fossil bridging? Tim Chase
2013-11-18 7:17 ` Johan Herland
2014-10-30 23:14 ` tofutim
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=20131117150010.675971d3@bigbox.christie.dr \
--to=git@tim.thechases.com \
--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.
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).