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

Re: Git -> fossil bridging?

From
TCTim Chase <git@tim.thechases.com>
Date
Nov 18, 2013, 00:26 UTC
Message-ID
<20131117182650.1ba89a8b@bigbox.christie.dr>
In-Reply-To
<575D57DB-026F-484E-8068-E7965395E902@gmail.com>
On 2013-11-17 14:43, Kyle J. McKay wrote:
> Sounds like you want to write a 'git-remote-fossil' helper so you
> can do something like:
> 
>    git clone fossil::http://sqlite.org/src
Pretty much.  Or at least something akin to git-svn where one would do
  git fossil clone http://some.fossil.url/path/to/repo.fossil
  # hack hack
  git commit
  # possibly some git-branch, git-merge, git-rebase, git-cherry-pick
  # lather, rinse, repeat
  git fossil push # or git fossil dcommit

I've not played with the git+hg or git+bzr bridges to see if they'd have a more useful interface that would better map to fossil. If so, imagine that's what I typed above ;-)

-tkc
Previous: Tim ChaseNext: Johan Herland
Message 2 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.