git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: git-svn rebase "problems"

From
JFJoe Fiorini <joe@faithfulgeek.org>
Date
Dec 2, 2008, 14:56 UTC
Message-ID
<73fd69b50812020656u3fd17015n267f694236982e5@mail.gmail.com>
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:
Show 24 quoted lines
> 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
Previous: Joe FioriniNext: Peter Harris
Message 2 of 4 in “git-svn rebase "problems"”
  1. Joe FioriniDec 1, 2008
  2. Joe FioriniDec 2, 2008
  3. Peter HarrisDec 2, 2008
  4. Michael J GruberDec 2, 2008

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.