From: "Jacob Helwig" <jacob.helwig@gmail.com>
To: davetron5000 <davetron5000@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: git svn rebase totally confused; just need some sorta reset
Date: Mon, 29 Dec 2008 14:04:04 -0800 [thread overview]
Message-ID: <8c9a060812291404m304e1920yd5ba7e40a6098b30@mail.gmail.com> (raw)
In-Reply-To: <cd7145c4-a4bb-4ef6-95db-7c4058b6774c@m16g2000vbp.googlegroups.com>
On Mon, Dec 29, 2008 at 13:39, davetron5000 <davetron5000@gmail.com> wrote:
> So, my repo is in a weird state. I have committed my changes to svn
> via git svn dcommit, and it appears that the svn repository has all my
> changes.
>
> However, git svn rebase fails with conflicts, on almost every single
> commit I've made. I think that ultimately, I merged a branch in
> numerous times and git seems confused. BUT, I don't really care about
> preserving that; I just want my master branch to be clean.
>
> Is there a way I can basically say: commit XXX is the same as the
> current HEAD of SVN, so treat things as if that's the case. i.e.
> treat things the same as if I had just done a clean git svn clone.
>
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
git checkout local-branch-you-want-to-fix
git reset --hard name-of-your-git-svn-branch (probably trunk, or
<prefix>/trunk, if you setup git-svn with the --prefix=<prefix>/
option).
This will wipe out anything you have in local-branch-you-want-to-fix,
and reset it to the same state that name-of-your-git-svn-branch is in.
-Jacob
next prev parent reply other threads:[~2008-12-29 22:05 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-29 21:39 git svn rebase totally confused; just need some sorta reset davetron5000
2008-12-29 22:04 ` Jacob Helwig [this message]
2008-12-29 22:04 ` Boyd Stephen Smith Jr.
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=8c9a060812291404m304e1920yd5ba7e40a6098b30@mail.gmail.com \
--to=jacob.helwig@gmail.com \
--cc=davetron5000@gmail.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