From: Sergey Yanovich <ynvich@gmail.com>
To: git@vger.kernel.org, J.Sixt@eudaptics.com
Subject: git tool to keep a subversion mirror
Date: Mon, 18 Jun 2007 17:47:31 +0300 [thread overview]
Message-ID: <11821780511231-git-send-email-ynvich@gmail.com> (raw)
In-Reply-To: 467686AB.504C619A@eudaptics.com
Johannes Sixt wrote:
> It is extremely difficult to tell whether the patch makes sense or is
> correct, if there is _no_ explanation what it is good for.
I agree 100%. I sent a fore-letter using git-send-email, but all parts got split.
Pasting it manually:
> I am actively using git for my project. Thanks everyone envolved.
>
> However, I got tired of administering own web server and registered my
> project at sourceforge. Unlike repo.or.cz (thanks again for everyone
> envolved), they do not provide git hosting. But a project without a
> source repository is non-sence.
>
> I am not in any way going to use Subversion after I tried git, but I
> need to be able to export to a Subversion repository. I found an
> excellent tool called 'git-svn'. However, the flawed nature of
> Subversion put shackles on normal git usage after you do 'git-svn init'.
>
> Since git is the best scm system, my situation is probably quite common.
> So I am filing these patches.
>
> There is a 'git-svn' command which does want I need, so I created a
> simple wrapper around it. I also found that 'git-svn commit-diff' is
> having a small trouble dealing with root <tree-ish>, which is corrected
> by an attached patch.
next reply other threads:[~2007-06-18 14:47 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-18 14:47 Sergey Yanovich [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-06-19 6:50 git tool to keep a subversion mirror Sergey Yanovich
2007-06-18 12:14 Sergey Yanovich
2007-06-17 19:38 Sergey Yanovich
2007-06-17 18:49 Sergey Yanovich
2007-06-17 21:09 ` Matthieu Moy
2007-06-18 6:42 ` Sergey Yanovich
2007-06-24 7:45 ` Jan Hudec
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=11821780511231-git-send-email-ynvich@gmail.com \
--to=ynvich@gmail.com \
--cc=J.Sixt@eudaptics.com \
--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).