{"thread":{"id":"24237","subject":"purpose of -r flag for git-svn fetch","startedAt":"2010-06-30T02:29:28Z","lastAt":"2010-06-30T13:32:14Z","messageCount":3,"participants":["Bradley Wagner","Will Palmer"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"144493","messageId":"AANLkTil_iADth0dvcar-nkqjRcmK4p1Sc3UcBmXJ9nQn@mail.gmail.com","threadId":"24237","inReplyTo":null,"subject":"purpose of -r flag for git-svn fetch","fromName":"Bradley Wagner","fromEmail":"bradley.wagner@hannonhill.com","sentAt":"2010-06-30T02:29:28Z","receivedAt":"2010-06-30T02:29:28Z","isPatch":false,"sender":{"key":"bradley.wagner@hannonhill.com","avatar":"https://gravatar.com/avatar/8304e5020b13d5f8102220fae2f5dd607a2e114dbe62bbd92c1ab38fe0b69fdb?d=mp&s=160"},"body":"I've tried doing git-svn fetch in batches because it takes too long to\ndo it all at once.\n\n    git svn -r1:5000 fetch\n    git svn -r5000:10000 fetch\n    git svn -r10000:15000 fetch\n\nStrangely, after this is done if I look in the history with \"git log\",\nI only see commits on master branch up through the 5000th revision of\nthe SVN repository. Someone told me to then call git-svn rebase to fix\nit. What does \"-r\" actually do when invoked on consecutive calls to\n\"git-svn fetch\" and why does git-svn rebase appear to fix it?\n\nI posted this question to Stackoverflow before realizing that this\nlist is a better audience for it:\nhttp://stackoverflow.com/questions/3144683/master-branch-missing-revisions-after-sequential-git-svn-fetch-calls\n\nThanks!\n"},{"id":"144509","messageId":"1277887235.2498.31.camel@wpalmer.simply-domain","threadId":"24237","inReplyTo":"AANLkTil_iADth0dvcar-nkqjRcmK4p1Sc3UcBmXJ9nQn@mail.gmail.com","subject":"Re: purpose of -r flag for git-svn fetch","fromName":"Will Palmer","fromEmail":"wmpalmer@gmail.com","sentAt":"2010-06-30T08:40:35Z","receivedAt":"2010-06-30T08:40:35Z","isPatch":false,"sender":{"key":"wmpalmer@gmail.com","avatar":"https://avatars.githubusercontent.com/u/357044?v=4"},"body":"On Tue, 2010-06-29 at 22:29 -0400, Bradley Wagner wrote:\n> I've tried doing git-svn fetch in batches because it takes too long to\n> do it all at once.\n> \n>     git svn -r1:5000 fetch\n>     git svn -r5000:10000 fetch\n>     git svn -r10000:15000 fetch\n> \n> Strangely, after this is done if I look in the history with \"git log\",\n> I only see commits on master branch up through the 5000th revision of\n> the SVN repository. Someone told me to then call git-svn rebase to fix\n> it. What does \"-r\" actually do when invoked on consecutive calls to\n> \"git-svn fetch\" and why does git-svn rebase appear to fix it?\n\nThe keyword here is \"fetch\". \"fetch\" only retrieves data into the\nremote-tracking branch (often called refs/remotes/git-svn), without\nupdating your local branches. \"git svn rebase\", on the other hand,\nrebases your currently-checked-out branch to be based on the git-svn\nremote ref. (note that \"git svn rebase\" does a \"git svn fetch\"\nbehind-the-scenes first, and is actually just \"git svn fetch\" followed\nby a normal \"git rebase\")\n\nThe concepts are the same as if you were using the regular git commands\n\"fetch\" and \"rebase\", so the man pages for those may offer some insight.\n\n> \n> I posted this question to Stackoverflow before realizing that this\n> list is a better audience for it:\n> http://stackoverflow.com/questions/3144683/master-branch-missing-revisions-after-sequential-git-svn-fetch-calls\n> \n> Thanks!\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n"},{"id":"144514","messageId":"AANLkTikSZgH42-G447IZ5j3s53ERW-H68iK9xRh9cGAG@mail.gmail.com","threadId":"24237","inReplyTo":"1277887235.2498.31.camel@wpalmer.simply-domain","subject":"Re: purpose of -r flag for git-svn fetch","fromName":"Bradley Wagner","fromEmail":"bradley.wagner@hannonhill.com","sentAt":"2010-06-30T13:32:14Z","receivedAt":"2010-06-30T13:32:14Z","isPatch":false,"sender":{"key":"bradley.wagner@hannonhill.com","avatar":"https://gravatar.com/avatar/8304e5020b13d5f8102220fae2f5dd607a2e114dbe62bbd92c1ab38fe0b69fdb?d=mp&s=160"},"body":"Hmm, this makes sense, but why does the initial fetch then update my\nlocal branch and if I call subsequent fetches without the \"-r\" it will\nfetch new revisions and update my local branch.\n\nOn Wed, Jun 30, 2010 at 4:40 AM, Will Palmer <wmpalmer@gmail.com> wrote:\n> On Tue, 2010-06-29 at 22:29 -0400, Bradley Wagner wrote:\n>> I've tried doing git-svn fetch in batches because it takes too long to\n>> do it all at once.\n>>\n>>     git svn -r1:5000 fetch\n>>     git svn -r5000:10000 fetch\n>>     git svn -r10000:15000 fetch\n>>\n>> Strangely, after this is done if I look in the history with \"git log\",\n>> I only see commits on master branch up through the 5000th revision of\n>> the SVN repository. Someone told me to then call git-svn rebase to fix\n>> it. What does \"-r\" actually do when invoked on consecutive calls to\n>> \"git-svn fetch\" and why does git-svn rebase appear to fix it?\n>\n> The keyword here is \"fetch\". \"fetch\" only retrieves data into the\n> remote-tracking branch (often called refs/remotes/git-svn), without\n> updating your local branches. \"git svn rebase\", on the other hand,\n> rebases your currently-checked-out branch to be based on the git-svn\n> remote ref. (note that \"git svn rebase\" does a \"git svn fetch\"\n> behind-the-scenes first, and is actually just \"git svn fetch\" followed\n> by a normal \"git rebase\")\n>\n> The concepts are the same as if you were using the regular git commands\n> \"fetch\" and \"rebase\", so the man pages for those may offer some insight.\n>\n>>\n>> I posted this question to Stackoverflow before realizing that this\n>> list is a better audience for it:\n>> http://stackoverflow.com/questions/3144683/master-branch-missing-revisions-after-sequential-git-svn-fetch-calls\n>>\n>> Thanks!\n>> --\n>> To unsubscribe from this list: send the line \"unsubscribe git\" in\n>> the body of a message to majordomo@vger.kernel.org\n>> More majordomo info at  http://vger.kernel.org/majordomo-info.html\n>\n>\n>\n"}]}