git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mike Gant <mwgant@gmail.com>
To: git@vger.kernel.org
Subject: repeatedly conflicting files when using git svn rebase
Date: Tue, 2 Aug 2011 18:41:09 -0600	[thread overview]
Message-ID: <CAPbp7P4XCsFJQL8zujkCbcLH+sEGMRUGES-Skre-OEB2vb=Nmg@mail.gmail.com> (raw)

All,

I have a problem where every time I run 'git svn rebase', I have the
same files with conflicts. Not only that but when I fix the conflict,
there is no change to add and I end up having to do 'git rebase --skip'.
Some of the differences are only whitespace but all are minor changes.
I've tried choosing the other part of the conflict (so I end up using
'git rebase --continue') but I still have the conflicts the next time I
run 'git svn rebase' . I should also note that this happens _everytime_
I run 'git svn rebase' even consecutive times with absolutely no other
operations in between. Does anyone have any suggestions?

(Unfortunately, I cannot share the repo.)

Thanks,
Mike

                 reply	other threads:[~2011-08-03  0:41 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='CAPbp7P4XCsFJQL8zujkCbcLH+sEGMRUGES-Skre-OEB2vb=Nmg@mail.gmail.com' \
    --to=mwgant@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).