git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Péter András Felvégi" <petschy@gmail.com>
To: git@vger.kernel.org
Subject: Question concerning svn -> git migration, merging
Date: Wed, 7 Jul 2010 14:29:20 +0200	[thread overview]
Message-ID: <AANLkTimBNgyUpBbaIRCyDKsXsvsqEu3SWUVTqT7un1W5@mail.gmail.com> (raw)

Hello,

I was happy with svn for a while, but recently I started a new branch
where I moved/renamed a few files, and merging became a less pleasant
experience: I have to manually generate diffs from the trunk and patch
the moved files on the branch (apart from remembering which revisions
were already merged).

I cloned the svn repo, checked out the branch, but when I try to merge
from master, I got a lot of conflicts. I guess this is because I did a
few merges already in svn (before the repo cloning), but git is not
aware of that. How could I merge the changes on trunk starting from a
specified revision number, so that only new stuff gets merged? If that
could be done, I would be happy with git-svn (future merges should be
easy), and never look back.

Please CC me in your reply, I'm not subscribed to the list.

Thanks, Peter

                 reply	other threads:[~2010-07-07 12:29 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=AANLkTimBNgyUpBbaIRCyDKsXsvsqEu3SWUVTqT7un1W5@mail.gmail.com \
    --to=petschy@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;
as well as URLs for NNTP newsgroup(s).