git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Git -> fossil bridging?

From
TCTim Chase <git@tim.thechases.com>
Date
Nov 17, 2013, 21:00 UTC
Message-ID
<20131117150010.675971d3@bigbox.christie.dr>

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: Tim Chase
Message 1 of 4 in “Git -> fossil bridging?”
  1. Tim ChaseNov 17, 2013
  2. Tim ChaseNov 18, 2013
  3. Johan HerlandNov 18, 2013
  4. tofutimOct 30, 2014

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.