{"thread":{"id":"20006","subject":"minor git-svn bug","startedAt":"2009-07-02T17:16:49Z","lastAt":"2009-07-03T06:24:16Z","messageCount":2,"participants":["doki_pen","Eric Wong"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"117375","messageId":"4A4CEB81.4080309@doki-pen.org","threadId":"20006","inReplyTo":null,"subject":"minor git-svn bug","fromName":"doki_pen","fromEmail":"doki_pen@doki-pen.org","sentAt":"2009-07-02T17:16:49Z","receivedAt":"2009-07-02T17:16:49Z","isPatch":false,"sender":{"key":"doki_pen@doki-pen.org","avatar":"https://gravatar.com/avatar/9723c8c8c66070b9a61d5ecd8670618fb039acc828b535845942f2499b2500a8?d=mp&s=160"},"body":"Is this the right place to bring up bugs?  Or only patches?  Anyway, I \nfound a small bug.\n\nDue to some strange structure on the svn host, I have manually added the \nfetch lines to the [svn-remote] section of config.  There are hundreds \nof branches and tags, so I only have lines for what I need.  I removed \none that I thought I didn't need anymore, and also removed the remote \ntracking branch.  When I discovered that I needed the branch again, I \nadded it back to svn-remotes and did a git svn fetch.  There were no new \ncommits on the branch, so the remote tracking branch was not recreated.  \nThe work around was to do a commit on the branch via svn, then git svn \nfetch.  This caused the remote tracking branch to reappear. \n"},{"id":"117402","messageId":"20090703062416.GA23128@dcvr.yhbt.net","threadId":"20006","inReplyTo":"4A4CEB81.4080309@doki-pen.org","subject":"Re: minor git-svn bug","fromName":"Eric Wong","fromEmail":"normalperson@yhbt.net","sentAt":"2009-07-03T06:24:16Z","receivedAt":"2009-07-03T06:24:16Z","isPatch":false,"sender":{"key":"e@80x24.org","avatar":null},"body":"doki_pen <doki_pen@doki-pen.org> wrote:\n> Is this the right place to bring up bugs?  Or only patches?  Anyway, I  \n> found a small bug.\n\nYes to both.  Also, feel free to Cc: me on git svn questions since\nit halves the chance of me losing track of it.\n\n> Due to some strange structure on the svn host, I have manually added the  \n> fetch lines to the [svn-remote] section of config.  There are hundreds  \n> of branches and tags, so I only have lines for what I need.  I removed  \n> one that I thought I didn't need anymore, and also removed the remote  \n> tracking branch.  When I discovered that I needed the branch again, I  \n> added it back to svn-remotes and did a git svn fetch.  There were no new  \n> commits on the branch, so the remote tracking branch was not recreated.   \n> The work around was to do a commit on the branch via svn, then git svn  \n> fetch.  This caused the remote tracking branch to reappear. --\n\nIf you have reflogs (on by default), then it would've been possible to\nrecreate the ref without hitting the network at all by creating the\nref based on the reflog.\n\ngit svn not detecting that a remote ref was manually removed was\nprobably caused by lingering metadata in .git/svn/$remote_branch/.\nClobbering that directory alone should've been sufficient for\n\"git svn fetch\" to work...\n\n-- \nEric Wong\n"}]}