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

sadly requesting help

From
Raymond Auge <raymond.auge@liferay.com>
Date
Mar 30, 2010, 22:43 UTC
Message-ID
<eaacf13c1003301543r45bb18b2n1d10d209f01e3326@mail.gmail.com>
Hello,
My name is Raymond Augé. I'm a senior developer on the Liferay Portal project.

We had a colo failure over the last day or so and lost the last 50-60 commits on our subversion repository (apparently, our backup strategy was not granular enough).

Luckily I use Git locally using the git-svn conduit.

I need to rewind my repository to an earlier revision and I'm hoping not to have to rebuild my local repo as the project is huge and takes me at least 16 hours to checkout using git-svn.

I tried using:
git svn reset --revision 49343
where 49343 is the last revision before the failure.
But I'm at git version 1.6.3.3 which doesn't support the "reset" operation.
I tried various incantations of
git reset --hard <hash>
where <hash> matched the subversion revision obtained
git svn find-rev 49343

But that didn't clear the svn indexes which still think it's at the much later revision.

Does anyone know if there is an alternate way to rewind the "svn" portion of my repo to "forget" about the revs since 49343 so that I can restart the fetch process and catch up with the new stream (the git side seems to be more than ok with it)?

Sincerely,

Raymond Augé Liferay Inc.

Next: Avery Pennarun
Message 1 of 4 in “sadly requesting help”
  1. Raymond AugeMar 30, 2010
  2. Avery PennarunMar 30, 2010
  3. Samuel TardieuMar 31, 2010
  4. Fwd: sadly requesting helpRaymond Auge, Apr 2, 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.