git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Joe Fiorini" <joe@faithfulgeek.org>
To: git@vger.kernel.org
Subject: Re: git-svn rebase "problems"
Date: Tue, 2 Dec 2008 09:56:45 -0500	[thread overview]
Message-ID: <73fd69b50812020656u3fd17015n267f694236982e5@mail.gmail.com> (raw)
In-Reply-To: <73fd69b50811301917j6535f289uf177976707914e46@mail.gmail.com>

Are there any other details I can provide to get an answer on this?

Thanks!
Joe

On Sun, Nov 30, 2008 at 10:17 PM, Joe Fiorini <joe@faithfulgeek.org> wrote:
> I'm having some problems with git svn rebase. I'm pretty sure this is
> just the way git works, not a problem per se. But it's causing trouble
> for me and my team.
> My team is currently on Subversion. I'm trying to convince some people
> that git is a good way to go.
>
> So I'm using git-svn. My team tends to commit to the svn server fairly
> often. It has happened more than once that, because git svn rebase
> applies each svn commit sequentially, some of the commits will
> conflict with each other - whether or not I have ever touched the
> file. Obviously, this is a big problem because if I've never touched
> the file, then I probably won't know exactly how to resolve the merge
> (the merge markers haven't been solely reliable).
>
> Is there anything I could do to get around this without having to
> merge code I'm unfamiliar with?
>
> Thanks all!
> Joe Fiorini
> --
> joe fiorini
> http://www.faithfulgeek.org
> // freelancing & knowledge sharing
>



-- 
joe fiorini
http://www.faithfulgeek.org
// freelancing & knowledge sharing

  reply	other threads:[~2008-12-02 14:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-12-01  3:17 git-svn rebase "problems" Joe Fiorini
2008-12-02 14:56 ` Joe Fiorini [this message]
2008-12-02 15:21   ` Peter Harris
2008-12-02 15:32   ` Michael J Gruber

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=73fd69b50812020656u3fd17015n267f694236982e5@mail.gmail.com \
    --to=joe@faithfulgeek.org \
    --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).