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

Re: git for subversion users

From
ALAlexander Litvinov <litvinov2004@gmail.com>
Date
Jun 26, 2007, 06:02 UTC
Message-ID
<200706261302.10056.litvinov2004@gmail.com>
In-Reply-To
<46809733.2060200@vilain.net>
В сообщении от 26 июня 2007 11:33 Sam Vilain написал(a):
> There's your first issue - misunderstanding branching :)  You should end
> up realising that every little idea or feature forms a code branch in
> the direction of its implementation, the choice is whether to let the
> branches twist and grow together or train them in clear directions.

git-svn has one major trouble with branch handling: merge two branches that are different branches at svn. Or simply start from different point from svn branch.

git-svn dcommit operation tries to figure out where to commit at svn side and fail at these conditions. It seems to me this happend becuse it uses special line at git's commit comment and in case of such merge it does not know there to commit. I did not found how to deal with this situation.

So, git-svn just a offline-capable version of svn client with linear history. Sure. you can fork your own branch and then merge it into svn branch again but you should really careful about this.

I even does not know the way to solve this problem.

--- Alexander Litvinov.

Previous: Patrick DoyleNext: Sam Vilain
Message 7 of 8 in “git for subversion users”
  1. Patrick DoyleJun 25, 2007
  2. Sam VilainJun 26, 2007
  3. Steven GrimmJun 26, 2007
  4. Sam VilainJun 26, 2007
  5. Sam VilainJun 26, 2007
  6. Patrick DoyleJun 26, 2007
  7. Alexander LitvinovJun 26, 2007
  8. subversion and merging [was: Re: git for subversion users]Sam Vilain, Jun 26, 2007

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.