From: Tim Chase <git@tim.thechases.com>
To: <git@vger.kernel.org>
Cc: "Kyle J. McKay" <mackyle@gmail.com>
Subject: Re: Git -> fossil bridging?
Date: Sun, 17 Nov 2013 18:26:50 -0600 [thread overview]
Message-ID: <20131117182650.1ba89a8b@bigbox.christie.dr> (raw)
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
next prev parent reply other threads:[~2013-11-18 0:25 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-17 21:00 Git -> fossil bridging? Tim Chase
[not found] ` <575D57DB-026F-484E-8068-E7965395E902@gmail.com>
2013-11-18 0:26 ` Tim Chase [this message]
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=20131117182650.1ba89a8b@bigbox.christie.dr \
--to=git@tim.thechases.com \
--cc=git@vger.kernel.org \
--cc=mackyle@gmail.com \
/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).