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

Re: git-svn breakage

From
EWEric Wong <normalperson@yhbt.net>
Date
Dec 12, 2006, 09:19 UTC
Message-ID
<20061212091918.GC8179@localdomain>
In-Reply-To
<4b3406f0612112123h13e346d2r5a3b196595bc017a@mail.gmail.com>
Dongsheng Song <dongsheng.song@gmail.com> wrote:
Show 8 quoted lines
> Hi,
> 
> I am trying to use git-svn synchronize git with svn.
> 
> When git-fetch failed midway, and resumed later.The git-svn log output
> fine, but git-log output only before resumed.
> 
> How can I fix it ?

git-svn only updates refs/heads/master to the last refs/remotes/git-svn revision on the first time fetch runs. Since git-log defaults to HEAD (which most likely points to refs/heads/master, use git-branch to find out), it'll only show the information in refs/heads/master.

So if you want to see the latest revisions that git-svn fetched, then use 'git log remotes/git-svn'

To pull changes into your working copy (or HEAD) use:
  git rebase refs/remotes/git-svn
Previous: Dongsheng Song
Message 2 of 2 in “git-svn breakage”
  1. Dongsheng SongDec 12, 2006
  2. Eric WongDec 12, 2006

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.