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

Re: Commit a series of patches to SVN without rebase

From
EWEric Wong <normalperson@yhbt.net>
Date
Jan 2, 2008, 03:11 UTC
Message-ID
<20080102031102.GA11711@untitled>
In-Reply-To
<slrnfmttoo.28m.joerg@alea.gnuu.de>
Jörg Sommer <joerg@alea.gnuu.de> wrote:
Show 16 quoted lines
> Hi Eric,
> 
> Eric Wong <normalperson@yhbt.net> wrote:
> > Jörg Sommer <joerg@alea.gnuu.de> wrote:
> >> I've a number of patches in git I want to send to a SVN repository. git
> >> svn dcommit does a rebase after each commit which makes the whole commit
> >> takes very long. Is it possible to skip the rebase? All patches are in
> >> one branch without merges, a simple chain. Is it save to use --no-rebase
> >> in this case?
> >
> > Right now, only if the changes don't depend on each other (they all
> > modify different files).
> 
> May I ask you what the rational behind doing a rebase every time is? Is
> it needed? Why is it not possible to send all commits and do one rebase
> after the last one?

Rebase is done to alert the user of potential conflicts before attempting to commit them to a remote repository. Formerly it was done to prevent potential clobbering of upstream changes if there were conflicts, but I think that's been rectified in recent months.

-- 
Eric Wong
Previous: Jörg Sommer
Message 4 of 4 in “Commit a series of patches to SVN without rebase”
  1. Jörg SommerDec 20, 2007
  2. Eric WongDec 22, 2007
  3. Jörg SommerDec 23, 2007
  4. Eric WongJan 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.