From: Tim Mazid <timmazid@hotmail•com>
To: git@vger•kernel.org
Subject: Re: drawbacks to svn server + git-svn vs git server?
Date: Wed, 28 Oct 2009 04:53:15 -0700 (PDT) [thread overview]
Message-ID: <26093326.post@talk.nabble.com> (raw)
In-Reply-To: <25994334.post@talk.nabble.com>
Hi,
I recently migrated from svn to git as well, but I've abandoned the svn
server altogether.
What I noticed is that the merges do not show up properly when you look at
the svn repo with git. Obviously because svn doesn't track that information.
I assume that such a problem would continue if you continued using the svn
server.
Personally, i would recommend migrating to git altogether, it isn't actually
that difficult. The only issue I had was fixing up the merges.
Sorry I can't be of more help, I'm just letting you know what issues I faced
with svn.
Good luck,
Tim.
Dexter Riley wrote:
>
> Hello. My group is currently using subversion on our version control
> server, but would like to move to git as a client. We are considering
> using git-svn, to avoid revalidating the server software. My question is,
> are there any major disadvantages to using git-svn versus git? I know
> that the git repository would be smaller. I'm more concerned about
> possible svn repository corruption, performance when pushing large merges
> back to svn, and any gotchas you might have encountered.
> Any advice would be greatly appreciated.
> Thanks,
> Ed
>
--
View this message in context: http://www.nabble.com/drawbacks-to-svn-server-%2B-git-svn-vs-git-server--tp25994334p26093326.html
Sent from the git mailing list archive at Nabble.com.
next prev parent reply other threads:[~2009-10-28 11:53 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-21 15:05 drawbacks to svn server + git-svn vs git server? Dexter Riley
2009-10-21 15:19 ` Pascal Obry
2009-10-21 16:05 ` Dmitry Potapov
2009-10-28 11:53 ` Tim Mazid [this message]
2009-10-28 12:19 ` Matthieu Moy
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=26093326.post@talk.nabble.com \
--to=timmazid@hotmail$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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