From: Raymond Auge <raymond.auge@liferay.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: sadly requesting help
Date: Tue, 30 Mar 2010 18:43:21 -0400 [thread overview]
Message-ID: <eaacf13c1003301543r45bb18b2n1d10d209f01e3326@mail.gmail.com> (raw)
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 reply other threads:[~2010-03-30 22:43 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 22:43 Raymond Auge [this message]
2010-03-30 23:14 ` sadly requesting help Avery Pennarun
2010-03-31 8:53 ` Samuel Tardieu
[not found] ` <x2weaacf13c1004011920r45db6608ub4a5b002a2caf335@mail.gmail.com>
2010-04-02 2:21 ` Fwd: " Raymond Auge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=eaacf13c1003301543r45bb18b2n1d10d209f01e3326@mail.gmail.com \
--to=raymond.auge@liferay.com \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).