{"thread":{"id":"20055","subject":"Re: \"git svn reset\" only resets current branch ?","startedAt":"2009-07-08T15:41:01Z","lastAt":"2009-07-08T15:41:01Z","messageCount":1,"participants":["Yann Dirson"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"117617","messageId":"50232.10.0.0.1.1247067661.squirrel@intranet.linagora.com","threadId":"20055","inReplyTo":null,"subject":"Re: \"git svn reset\" only resets current branch ?","fromName":"Yann Dirson","fromEmail":"ydirson@linagora.com","sentAt":"2009-07-08T15:41:01Z","receivedAt":"2009-07-08T15:41:01Z","isPatch":false,"sender":{"key":"ydirson@linagora.com","avatar":null},"body":"> On Tue, Jul 07, 2009 at 10:01:08AM +0200, Yann Dirson wrote:\n>>\n>> As an alternative, we could also allow \"git svn reset\" to take us back\n>> into the future to undo any such mistake without refetching.\n>\n> You can't do that directly, since data is destroyed (specifically, the\n> rev_map is truncated back to the selected revision).  However, you can\n> \"git reset\" the branch back to where it was using the reflog, and then\n> the next git-svn command you run will rebuild the rev_map from the\n> comment metadata (obviously you're out of luck if you set \"no_metadata\").\n>\n> It's possible that \"git-svn reset\" should be saving something like\n> ORIG_HEAD (comments welcome) but that does conflict with the idea of\n> adding \"--all\" or defaulting to \"--all\" behavior.\n\nWell, adding --all would probably be better after all.\n"}]}