From: Steven Michalske <smichalske@gmail.com>
To: William Hall <will@gnatter.net>
Cc: git@vger.kernel.org
Subject: Re: SVN migration
Date: Wed, 16 Jun 2010 17:41:49 -0700 [thread overview]
Message-ID: <7B0F34CE-9C9F-4FC3-AD96-8B1B8DD4359B@gmail.com> (raw)
In-Reply-To: <4C1957EF.6070504@gnatter.net>
On Jun 16, 2010, at 4:02 PM, William Hall wrote:
>
> The issue is the dcommit operation from the bridge. The rebase part of this re-writes the commit messages to include the SVN commit-ids which is nice, but screws up the push/pulls between the bridge and the bare repo.
Look into svn.noMetadata configuration option. It will prevent you from rebuilding the svn to git bridge if something seriously goes wrong, but it prevents the messages from changing.
svn-remote.<name>.noMetadata
This gets rid of the git-svn-id: lines at the end of every commit.
If you lose your .git/svn/git-svn/.rev_db file, git svn will not be able to rebuild it and you won't be able to fetch again, either. This is fine for one-shot imports.
The git svn log command will not work on repositories using this, either. Using this conflicts with the useSvmProps option for (hopefully) obvious reasons
next prev parent reply other threads:[~2010-06-17 0:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-16 23:02 SVN migration William Hall
2010-06-17 0:41 ` Steven Michalske [this message]
2010-06-17 10:33 ` William Hall
2010-06-17 16:27 ` William Hall
2010-06-21 21:12 ` Joshua Shrader
2010-06-21 22:26 ` William Hall
2010-06-26 10:33 ` William Hall
2010-07-03 11:37 ` David Bainbridge
2010-07-04 17:55 ` William Hall
2010-07-04 22:01 ` David Bainbridge
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7B0F34CE-9C9F-4FC3-AD96-8B1B8DD4359B@gmail.com \
--to=smichalske@gmail.com \
--cc=git@vger.kernel.org \
--cc=will@gnatter.net \
/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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).