From: Junio C Hamano <gitster@pobox.com>
To: Daniel Barkalow <barkalow@iabervon.org>
Cc: git@vger.kernel.org
Subject: Re: What's cooking in git.git (Mar 2009, #04; Sat, 14)
Date: Mon, 16 Mar 2009 17:19:25 -0700 [thread overview]
Message-ID: <7v4oxtuhki.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <alpine.LNX.1.00.0903161834530.19665@iabervon.org> (Daniel Barkalow's message of "Mon, 16 Mar 2009 19:11:03 -0400 (EDT)")
Daniel Barkalow <barkalow@iabervon.org> writes:
> On Sat, 14 Mar 2009, Junio C Hamano wrote:
>
>> * db/foreign-scm (Sun Jan 11 15:12:10 2009 -0500) 3 commits
>> - Support fetching from foreign VCSes
>> - Add specification of git-vcs helpers
>> - Add "vcs" config option in remotes
>>
>> The "spec" did not seem quite well cooked yet, but in the longer term I
>> think something like this to allow interoperating with other SCMs as if
>> the other end is a native git repository is a very worthy goal.
>
> I recently figured out a way to alter the transport API slightly to make
> it possible to attach foreign VCSes there. This amounts to allowing
> get_refs_list() to leave the sha1s null, and allowing fetch() to set them.
> This just requires a copy of a ref list in the clone path, and a check to
> make null (for not having a ref) not match null (for not knowing the hash
> of the ref) in the fetch logic.
>
> I think I will end up changing the spec, mostly to allow a single
> non-trivial call to the helper to provide both the list of refs and the
> fast-import stream; this matches how the pack protocol works (except, of
> course, that the initial list doesn't have hashes, and the output goes to
> fast-import instead of unpack-objects). I'm going to rebase the series at
> some point, but I've been focused more on the more core transport and
> remote stuff now that I think I can go through that.
Thanks for a wonderful news.
next prev parent reply other threads:[~2009-03-17 0:21 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-15 6:28 What's cooking in git.git (Mar 2009, #04; Sat, 14) Junio C Hamano
2009-03-16 23:11 ` Daniel Barkalow
2009-03-17 0:19 ` Junio C Hamano [this message]
2009-03-17 10:28 ` push.default, was " Johannes Schindelin
2009-03-17 21:30 ` Nanako Shiraishi
2009-03-17 22:53 ` Johannes Schindelin
2009-03-17 23:47 ` Junio C Hamano
2009-03-18 0:40 ` Johannes Schindelin
2009-03-18 1:05 ` Junio C Hamano
2009-03-17 10:31 ` notes, " Johannes Schindelin
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=7v4oxtuhki.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=barkalow@iabervon.org \
--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).