Git development
 help / color / mirror / Atom feed
From: "Boyd Stephen Smith Jr." <bss@iguanasuicide.net>
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 16:04:56 -0600	[thread overview]
Message-ID: <200812291605.00112.bss@iguanasuicide.net> (raw)
In-Reply-To: <cd7145c4-a4bb-4ef6-95db-7c4058b6774c@m16g2000vbp.googlegroups.com>

[-- Attachment #1: Type: text/plain, Size: 1113 bytes --]

On Monday 2008 December 29 15:39:45 davetron5000 wrote:
> 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.

No, commits are immutable and their "name" is based on their contents.  
However, if you've fetched the current HEAD of SVN, you've already got a 
commit that corresponds (roughly) to the HEAD of SVN.

> i.e. 
> treat things the same as if I had just done a clean git svn clone.

On my git-svn created repository, I have a special ref "git-svn" that appears 
to refer to the "HEAD of SVN" commit.  ("git branch -a" shows it.)  If that's 
also the case with you:

git branch -m master master.save
git checkout -b master git-svn
# Make sure you are seeing what you want.
git branch -D master.save

should get you to where you want.

Heck, "git reset git-svn" might work.
-- 
Boyd Stephen Smith Jr.                     ,= ,-_-. =. 
bss@iguanasuicide.net                     ((_/)o o(\_))
ICQ: 514984 YM/AIM: DaTwinkDaddy           `-'(. .)`-' 
http://iguanasuicide.net/                      \_/     

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]

      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
2008-12-29 22:04 ` Boyd Stephen Smith Jr. [this message]

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=200812291605.00112.bss@iguanasuicide.net \
    --to=bss@iguanasuicide.net \
    --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