git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Ping Yin <pkufranky@gmail.com>
To: "Ævar Arnfjörð Bjarmason" <avarab@gmail.com>
Cc: git mailing list <git@vger.kernel.org>
Subject: Re: How to continue to run 'git svn fetch' for a repo with no git-svn  metadata
Date: Wed, 28 Apr 2010 00:04:24 +0800	[thread overview]
Message-ID: <n2p46dff0321004270904gc590ef83v4b338719c4c18637@mail.gmail.com> (raw)
In-Reply-To: <z2l51dd1af81004270751yf026e946p4b00552eaf4f2632@mail.gmail.com>

On Tue, Apr 27, 2010 at 10:51 PM, Ævar Arnfjörð Bjarmason
<avarab@gmail.com> wrote:
> Read these:
>
>    http://code.google.com/p/chromium/wiki/UsingGit#Initial_Setup
>    http://trac.parrot.org/parrot/wiki/git-svn-tutorial
>
> This should probably be in the git-svn documentation itself.

Thanks. The last link explains very clear. I just copy and paste from it.

Adding git-svn metadata to the github clone

If you want to re-populate the SVN metadata that can quickly be done
by taking your up-to-date clone of leto's repo off of gihub and adding
this to your .git/config

    [svn-remote "svn"]
            url = https://svn.parrot.org/parrot
            fetch = trunk:refs/remotes/trunk
Then run this command to find the "top commit"

     git show origin/upstream | head -n 1
and put that commit hash into a file .git/refs/remotes/trunk
(obviously replace the has with the one from the above command)

     echo c85aaa38b99cedb087e5f6fb69ce6d4a6ac57a0b > .git/refs/remotes/trunk
and finally

     git svn fetch

      reply	other threads:[~2010-04-27 16:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-04-27  9:48 How to continue to run 'git svn fetch' for a repo with no git-svn metadata Ping Yin
2010-04-27 14:51 ` Ævar Arnfjörð Bjarmason
2010-04-27 16:04   ` Ping Yin [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=n2p46dff0321004270904gc590ef83v4b338719c4c18637@mail.gmail.com \
    --to=pkufranky@gmail.com \
    --cc=avarab@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;
as well as URLs for NNTP newsgroup(s).