From: Daniel Barkalow <barkalow@iabervon.org>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: Re: [RFC] git pull and importers
Date: Sat, 7 Apr 2007 13:41:39 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.64.0704071323010.27922@iabervon.org> (raw)
In-Reply-To: <7v1wiwfeo5.fsf@assigned-by-dhcp.cox.net>
On Sat, 7 Apr 2007, Junio C Hamano wrote:
> Daniel Barkalow <barkalow@iabervon.org> writes:
>
> > Which would mean that it would use "git svn fetch" instead of "git fetch"
> > for that remote, and "git svn fetch" would use that config section instead
> > of its current config section.
> >
> > Any reason this couldn't be made to work?
>
> No reason. Making git-$(scm)import to behave more like
> git-fetch-pack backend was one of the longstanding items on my
> wishlist. I think "cvsimport -i" could mostly be usable in the
> current shape for that, but I do not know about others.
I picked git-svn in part because it looks especially obvious; it even
calls fetch "fetch". Not that that *really* counts for much, but I can
pretend.
> Especially I do not interoperate with any SVN repositories
> myself, so I cannot scratch your itch.
I'll look into it, if the config option scheme looks reasonable to you.
> However, I suspect you could help me with a code I've been
> struggling with on-and-off lately. Do you still remember
> unpack-trees code?
I'm not sure how similar it is these days to the code I worked on (which
was called "read-tree", I think), but I'll take a look.
-Daniel
*This .sig left intentionally blank*
next prev parent reply other threads:[~2007-04-07 17:41 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-07 2:48 [RFC] git pull and importers Daniel Barkalow
2007-04-07 14:21 ` Junio C Hamano
2007-04-07 17:41 ` Daniel Barkalow [this message]
2007-04-07 20:24 ` Eric Wong
2007-04-07 21:32 ` Junio C Hamano
2007-04-07 21:50 ` Eric Wong
2007-04-07 23:12 ` Daniel Barkalow
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=Pine.LNX.4.64.0704071323010.27922@iabervon.org \
--to=barkalow@iabervon.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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).