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

Re: git svn dcommit <branch> committed to trunk anyway

From
Thomas Rast <trast@student.ethz.ch>
Date
May 7, 2012, 09:44 UTC
Message-ID
<87txzsba0o.fsf@thomas.inf.ethz.ch>
In-Reply-To
<CAH3AnroP+ckzgijibPDEupBCfUFu5Bwsq8YP58h+igXoJyJEyg@mail.gmail.com>
Jon Seymour <jon.seymour@gmail.com> writes:
Show 8 quoted lines
> I expected git svn dcommit <branch> to push commits into the svn
> branch called <branch> (a repo relative URL of
> /branches/foobar1/foobar2/<branch>)
>
> However, it decided to push into trunk instead, which was not the
> intended effect.
>
> What have I misunderstood about how git svn dcommit is supposed to work?

Did the commits you dcommitted have any git-svn-id lines? It dcommits (or at least it's supposed to :-) in the directory listed in the git-svn-id line found by (roughly)

  git log --first-parent -1 --grep=^git-svn-id:
-- 
Thomas Rast
trast@{inf,student}.ethz.ch
Previous: Jon SeymourNext: Jon Seymour
Message 2 of 5 in “git svn dcommit <branch> committed to trunk anyway”
  1. Jon SeymourMay 6, 2012
  2. Thomas RastMay 7, 2012
  3. Jon SeymourMay 7, 2012
  4. Thomas RastMay 7, 2012
  5. Jon SeymourMay 7, 2012

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.