From: "Pap Lôrinc" <paplorinc@yahoo.com>
To: David Aguilar <davvid@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: Parallel refactoring and git merge nightmare
Date: Wed, 11 Apr 2012 22:23:57 -0700 (PDT) [thread overview]
Message-ID: <1334208237.82681.YahooMailNeo@web160606.mail.bf1.yahoo.com> (raw)
In-Reply-To: <CAJDDKr6v6uPLoAQ96fP7JM5F0_WHqfbaD=QKyfrWPWd2St7tKQ@mail.gmail.com>
>> Hello! :)
>>
>> We are working in parallel on the refactoring of a
>> small project. The team uses SVN and I decided to give GIT a chance to
>> demonstrate it's merging capabilities I've read so much good about :).
>>
>> However
>> - I must be doing something VERY wrong - every time I try to merge from
>> the remote svn (git svn fetch and git merge remotebranch) into my
>> branch, I get hundreds of conflicts, mostly because of moved folders.
>
>Google is your friend
>
>https://wiki.kuali.org/display/KULRICE/git-svn+how+to
>
>http://flavio.castelli.name/howto_use_git_with_svn
>
>http://viget.com/extend/effectively-using-git-with-subversion
>
>http://java.dzone.com/articles/how-start-using-git-svn-based
>--
>David
I have no idea why you guys think I'm an idiot.
I have read every link I could find (most of the Pro Git book and watched several hours of git video tutorials). The problem is not with GIT-SVN, it's with the GIT merge, more specifically with a simultaneous modify and move, which conflicts probably because it is detected as a modify and delete.
Could someone please be a little more friendly, I need advice on how to solve hundreds of git merge conflicts (eg. parallel move and modify, which should have been merged automatically).
Thanks,
Lőrinc
next prev parent reply other threads:[~2012-04-12 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-11 16:13 Parallel refactoring and git merge nightmare Pap Lôrinc
2012-04-11 16:49 ` Michael Witten
2012-04-12 3:27 ` David Aguilar
2012-04-12 5:23 ` Pap Lôrinc [this message]
2012-04-12 5:41 ` Andrew Ardill
2012-04-12 5:49 ` David Barr
2012-04-12 13:52 ` Pap Lôrinc
2012-04-12 16:03 ` Eugene Sajine
2012-04-12 5:41 ` Jeff King
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=1334208237.82681.YahooMailNeo@web160606.mail.bf1.yahoo.com \
--to=paplorinc@yahoo.com \
--cc=davvid@gmail.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