StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>It is possible <code>git push</code> or <code>git bundle</code> do not include svn metadata.</p> <p>But according to <a href="http://www.vilain.net/talks/git-svn/intro.html#howto-track-rebuildmeta" rel="nofollow noreferrer"><code>git svn</code> intro</a>, you could then try and restore those svn metadata.<br> (disclaimer: not tested directly)</p> <blockquote> <p><strong>Rebuilding git-svn metadata</strong></p> </blockquote> <p>If you copied the repository from somewhere else (eg, from <code>repo.utsl.gen.nz</code>) via <code>git-clone</code>, or if you just blew it away, then you won't have any SVN metadata - just commits.<br> In that case, you need to rebuild your SVN metadata, for instance, for just keeping trunk up to date - <code>git-svn</code> will rebuild its metadata when you run <code>git-svn fetch</code>.</p> <pre><code>$ git update-ref refs/remotes/trunk origin/svn/trunk $ git svn init https://svn.perl.org/parrot/trunk Using higher level of URL: https://svn.perl.org/parrot/trunk => https://svn.perl.org/parrot $ git svn fetch Rebuilding .git/svn/git-svn/.rev_db.d31e2699-5ff4-0310-a27c-f18f2fbe73fe ... r17220 = 78ad11bf2f61b35e1cb32a978ab546d198be8a2e r17219 = 605264b06d84670ec402d7a7a21c0016cae3a928 r17218 = a8ceba9c503d2be8e8e69a3df454017322906cf5 ... </code></pre> <blockquote> <p>The key thing to remember with rebuilding <code>git-svn</code> metadata is to make the refs look just like they would look from a fresh import; you can do this using <code>git update-ref</code> as above, by copying refs files around inside <code>.git/refs/</code>, or using <code>git pack-refs</code> then editing <code>.git/packed-refs</code>.<br> To test that you got it right, use <code>git show-ref</code> - perhaps compare with a fresh SVN <code>HEAD</code> clone. </p> </blockquote>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload