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

purpose of -r flag for git-svn fetch

From
Bradley Wagner <bradley.wagner@hannonhill.com>
Date
Jun 30, 2010, 02:29 UTC
Message-ID
<AANLkTil_iADth0dvcar-nkqjRcmK4p1Sc3UcBmXJ9nQn@mail.gmail.com>

I've tried doing git-svn fetch in batches because it takes too long to do it all at once.

    git svn -r1:5000 fetch
    git svn -r5000:10000 fetch
    git svn -r10000:15000 fetch

Strangely, after this is done if I look in the history with "git log", I only see commits on master branch up through the 5000th revision of the SVN repository. Someone told me to then call git-svn rebase to fix it. What does "-r" actually do when invoked on consecutive calls to "git-svn fetch" and why does git-svn rebase appear to fix it?

I posted this question to Stackoverflow before realizing that this list is a better audience for it: http://stackoverflow.com/questions/3144683/master-branch-missing-revisions-after-sequential-git-svn-fetch-calls

Thanks!
Next: Will Palmer
Message 1 of 3 in “purpose of -r flag for git-svn fetch”
  1. Bradley WagnerJun 30, 2010
  2. Will PalmerJun 30, 2010
  3. Bradley WagnerJun 30, 2010

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.