From: Avery Pennarun <apenwarr@gmail.com>
To: Raymond Auge <raymond.auge@liferay.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: sadly requesting help
Date: Tue, 30 Mar 2010 19:14:15 -0400 [thread overview]
Message-ID: <32541b131003301614iad1fedfl85020ba9e285045f@mail.gmail.com> (raw)
In-Reply-To: <eaacf13c1003301543r45bb18b2n1d10d209f01e3326@mail.gmail.com>
On Tue, Mar 30, 2010 at 6:43 PM, Raymond Auge <raymond.auge@liferay.com> wrote:
> 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 don't know about this option, but if it sounds like it would work,
why not just upgrade your git? It's very easy (easier than most
programs) to compile it from source.
> I tried various incantations of
>
> git reset --hard <hash>
>
> where <hash> matched the subversion revision obtained
You probably need something like:
git update-ref refs/remotes/git-svn <commitid>
Where "refs/remotes/git-svn" is the ref that git-svn is using (you can
usually find this with "git branch -r" and then prepend refs/remotes/
to the name it gives you). And <commitid> is the commit you want to
be the "most recent" one from svn.
You may or may not also need to delete your svn cache dir (.git/svn).
This should be harmless since git-svn can regenerate it later by
reading through your local commits.
MAKE SURE YOU BACKUP YOUR REPO BEFORE TRYING ANY OF THIS ADVICE.
Good luck,
Avery
next prev parent reply other threads:[~2010-03-30 23:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-03-30 22:43 sadly requesting help Raymond Auge
2010-03-30 23:14 ` Avery Pennarun [this message]
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=32541b131003301614iad1fedfl85020ba9e285045f@mail.gmail.com \
--to=apenwarr@gmail.com \
--cc=git@vger.kernel.org \
--cc=raymond.auge@liferay.com \
/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).