Re: [RFC] git pull and importers

Eric Wong [off-list ref] writes:

When git-fetch is called without any remote arguments, it would look for
[remote "origin"] as it does now.  However, if no [remote "..."]
sections are found (as is common with importer-created repos), it would
try other importers: [svn-remote "svn"], (and hopefully one day
[cvs-remote "cvs"], [arch-remote "arch"], ...).

I wonder why wouldn't the alternative of noticing the URL scheme
of '[remote "svn"] url' variable is "svn://".  That is...

	[remote "gitrepo"]
        	url = git://example.com/repo.git/
		fetch = refs/heads/*:refs/remotes/gitrepo/*
	[remote "svnrepo"]
        	url = svn://example.com/repo.svn/
                fetch = trunk:refs/remotes/svnrepo/trunk
	[remote "cvsrepo"]
        	url = cvs://example.com/repo.cvs/
                fetch = HEAD:refs/remotes/cvsrepo/

The sections would probably can have importer specific options
besides usual url/fetch.

Junio C Hamano [off-list ref] wrote:

Eric Wong [off-list ref] writes:

quoted

When git-fetch is called without any remote arguments, it would look for
[remote "origin"] as it does now.  However, if no [remote "..."]
sections are found (as is common with importer-created repos), it would
try other importers: [svn-remote "svn"], (and hopefully one day
[cvs-remote "cvs"], [arch-remote "arch"], ...).

I wonder why wouldn't the alternative of noticing the URL scheme
of '[remote "svn"] url' variable is "svn://".  That is...

SVN repositories can also be http:// or https://, too.

-- 
Eric Wong