From: Bruce Stephens <bruce.stephens@isode.com>
To: Tim Visher <tim.visher@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Git -> SVN importing
Date: Tue, 03 Feb 2009 15:38:43 +0000 [thread overview]
Message-ID: <80k5871qf0.fsf@tiny.isode.net> (raw)
In-Reply-To: <c115fd3c0902030717u6a8f3bbck3027cf74715c79a4@mail.gmail.com> (Tim Visher's message of "Tue\, 3 Feb 2009 10\:17\:17 -0500")
Tim Visher <tim.visher@gmail.com> writes:
[...]
> I figured that someone would have to have done this before since
> git-svn is so magical. However, I thought I'd ask.
>
> What's the story?
My guess is there aren't many people who've migrated from git to svn.
(And fewer who'd admit to it on this mailing list.)
[...]
next prev parent reply other threads:[~2009-02-03 15:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-03 15:17 Git -> SVN importing Tim Visher
2009-02-03 15:38 ` Bruce Stephens [this message]
2009-02-03 15:39 ` Edward Z. Yang
2009-02-03 17:29 ` 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=80k5871qf0.fsf@tiny.isode.net \
--to=bruce.stephens@isode.com \
--cc=git@vger.kernel.org \
--cc=tim.visher@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.