From: "Peter Harris" <peter@peter.is-a-geek.org>
To: "Grzegorz Kossakowski" <grek@tuffmail.com>
Cc: "Michael J Gruber" <git@drmicha.warpmail.net>, git@vger.kernel.org
Subject: Re: How to clone git repository with git-svn meta-data included?
Date: Mon, 8 Dec 2008 13:40:02 -0500 [thread overview]
Message-ID: <eaa105840812081040s1036b79an9914c1f74d6d7f6a@mail.gmail.com> (raw)
In-Reply-To: <493D66BB.3060907@tuffmail.com>
On Mon, Dec 8, 2008 at 1:26 PM, Grzegorz Kossakowski wrote:
>
> After doing that git svn rebase resulted in:
> [really long list of revisions]
> r707379 = f61a2d30b6ac5a5136b46fa2b9b5b91e4763feb1
> r710118 = 40997fe552e8581b75b08fed41a6b63a33d58bdf
> r720135 = a8160766ec40fd7ebf95bfa7cebfa50dfa2f9c3a
> r720180 = b094a222bab3671c8277087e7a96589ec76dd5e4
> r720182 = 736b8ed6519c64ad120de2ccf08f135062ee09db
> Done rebuilding .git/svn/origin/trunk/.rev_map.13f79535-47bb-0310-9956-ffa450edef68
> Current branch master is up to date.
>
> Is this expected output?
Yes. The rfoo = sha1hash part is git-svn rebuilding its index.
"Current branch master is up to date" is git-svn calling "git rebase
<svn-branch>", and git saying that there is nothing to do, since there
have been no svn commits to that branch since the last time you ran
git svn rebase (or since you cloned the git mirror, or since the last
time the git mirror pulled from svn).
Peter Harris
next prev parent reply other threads:[~2008-12-08 18:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-06 12:15 How to clone git repository with git-svn meta-data included? Grzegorz Kossakowski
2008-12-07 8:43 ` Jacob Helwig
2008-12-08 0:03 ` Nick Andrew
2008-12-07 16:57 ` Peter Harris
2008-12-07 19:08 ` Grzegorz Kossakowski
2008-12-07 20:30 ` Peter Harris
2008-12-07 22:02 ` Grzegorz Kossakowski
2008-12-07 23:51 ` Peter Harris
2008-12-08 13:10 ` Michael J Gruber
2008-12-08 18:26 ` Grzegorz Kossakowski
2008-12-08 18:40 ` Peter Harris [this message]
2008-12-08 18:43 ` Grzegorz Kossakowski
2008-12-09 9:08 ` Sam Vilain
2008-12-09 20:57 ` Grzegorz Kossakowski
2008-12-09 8:53 ` Michael J Gruber
2008-12-08 16:10 ` Shawn O. Pearce
2008-12-08 19:04 ` Grzegorz Kossakowski
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=eaa105840812081040s1036b79an9914c1f74d6d7f6a@mail.gmail.com \
--to=peter@peter.is-a-geek.org \
--cc=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=grek@tuffmail.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).