</dt>\r
<dd>\r
<p>\r
- Make git-svn less verbose. This only affects git-svn if you\r
- have the SVN::* libraries installed and are using them.\r
+ Make git-svn less verbose.\r
</p>\r
</dd>\r
<dt>\r
started tracking a branch and never tracked the trunk it was\r
descended from.\r
</p>\r
-<div class="literalblock">\r
-<div class="content">\r
-<pre><tt>This relies on the SVN::* libraries to work.</tt></pre>\r
-</div></div>\r
<p>repo-config key: svn.followparent</p>\r
</dd>\r
<dt>\r
for tracking the remote.</p>\r
</dd>\r
<dt>\r
---no-ignore-externals\r
-</dt>\r
-<dd>\r
-<p>\r
-Only used with the <em>fetch</em> and <em>rebuild</em> command.\r
-</p>\r
-<p>This command has no effect when you are using the SVN::*\r
-libraries with git, svn:externals are always avoided.</p>\r
-<p>By default, git-svn passes --ignore-externals to svn to avoid\r
-fetching svn:external trees into git. Pass this flag to enable\r
-externals tracking directly via git.</p>\r
-<p>Versions of svn that do not support --ignore-externals are\r
-automatically detected and this flag will be automatically\r
-enabled for them.</p>\r
-<p>Otherwise, do not enable this flag unless you know what you're\r
-doing.</p>\r
-<p>repo-config key: svn.noignoreexternals</p>\r
-</dd>\r
-<dt>\r
--ignore-nodate\r
</dt>\r
<dd>\r
<div class="content">\r
<pre><tt> git-svn fetch 375=$(git-rev-parse HEAD)</tt></pre>\r
</div></div>\r
-<h3>Advanced Example: Tracking a Reorganized Repository</h3>\r
-<p>Note: this example is now obsolete if you have SVN::* libraries\r
-installed. Simply use --follow-parent when fetching.</p>\r
<p>If you're tracking a directory that has moved, or otherwise been\r
branched or tagged off of another directory in the repository and you\r
-care about the full history of the project, then you can read this\r
-section.</p>\r
-<p>This is how Yann Dirson tracked the trunk of the ufoai directory when\r
-the /trunk directory of his repository was moved to /ufoai/trunk and\r
-he needed to continue tracking /ufoai/trunk where /trunk left off.</p>\r
+care about the full history of the project, then you can use\r
+the --follow-parent option.</p>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt> # This log message shows when the repository was reorganized:\r
- r166 | ydirson | 2006-03-02 01:36:55 +0100 (Thu, 02 Mar 2006) | 1 line\r
- Changed paths:\r
- D /trunk\r
- A /ufoai/trunk (from /trunk:165)\r
-\r
- # First we start tracking the old revisions:\r
- GIT_SVN_ID=git-oldsvn git-svn init \\r
- https://svn.sourceforge.net/svnroot/ufoai/trunk\r
- GIT_SVN_ID=git-oldsvn git-svn fetch -r1:165\r
-\r
- # And now, we continue tracking the new revisions:\r
- GIT_SVN_ID=git-newsvn git-svn init \\r
- https://svn.sourceforge.net/svnroot/ufoai/ufoai/trunk\r
- GIT_SVN_ID=git-newsvn git-svn fetch \\r
- 166=`git-rev-parse refs/remotes/git-oldsvn`</tt></pre>\r
+<pre><tt> git-svn fetch --follow-parent</tt></pre>\r
</div></div>\r
</div>\r
<h2>BUGS</h2>\r
<div class="sectionbody">\r
-<p>If you are not using the SVN::* Perl libraries and somebody commits a\r
-conflicting changeset to SVN at a bad moment (right before you commit)\r
-causing a conflict and your commit to fail, your svn working tree\r
-($GIT_DIR/git-svn/tree) may be dirtied. The easiest thing to do is\r
-probably just to rm -rf $GIT_DIR/git-svn/tree and run <em>rebuild</em>. You\r
-can avoid this problem entirely by using <em>dcommit</em>.</p>\r
<p>We ignore all SVN properties except svn:executable. Too difficult to\r
map them since we rely heavily on git write-tree being _exactly_ the\r
same on both the SVN and git working trees and I prefer not to clutter\r
</div>\r
<div id="footer">\r
<div id="footer-text">\r
-Last updated 08-Jan-2007 06:53:20 UTC\r
+Last updated 10-Jan-2007 05:05:02 UTC\r
</div>\r
</div>\r
</body>\r
-q::
--quiet::
- Make git-svn less verbose. This only affects git-svn if you
- have the SVN::* libraries installed and are using them.
+ Make git-svn less verbose.
--repack[=<n>]::
--repack-flags=<flags>
started tracking a branch and never tracked the trunk it was
descended from.
- This relies on the SVN::* libraries to work.
-
repo-config key: svn.followparent
--no-metadata::
"git-svn-HEAD" instead of "remotes/git-svn" as the branch
for tracking the remote.
---no-ignore-externals::
-Only used with the 'fetch' and 'rebuild' command.
-
-This command has no effect when you are using the SVN::*
-libraries with git, svn:externals are always avoided.
-
-By default, git-svn passes --ignore-externals to svn to avoid
-fetching svn:external trees into git. Pass this flag to enable
-externals tracking directly via git.
-
-Versions of svn that do not support --ignore-externals are
-automatically detected and this flag will be automatically
-enabled for them.
-
-Otherwise, do not enable this flag unless you know what you're
-doing.
-
-repo-config key: svn.noignoreexternals
-
--ignore-nodate::
Only used with the 'fetch' command.
git-svn fetch 375=$(git-rev-parse HEAD)
------------------------------------------------
-Advanced Example: Tracking a Reorganized Repository
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-Note: this example is now obsolete if you have SVN::* libraries
-installed. Simply use --follow-parent when fetching.
-
If you're tracking a directory that has moved, or otherwise been
branched or tagged off of another directory in the repository and you
-care about the full history of the project, then you can read this
-section.
-
-This is how Yann Dirson tracked the trunk of the ufoai directory when
-the /trunk directory of his repository was moved to /ufoai/trunk and
-he needed to continue tracking /ufoai/trunk where /trunk left off.
+care about the full history of the project, then you can use
+the --follow-parent option.
-------------------------------------------------------------------------
- # This log message shows when the repository was reorganized:
- r166 | ydirson | 2006-03-02 01:36:55 +0100 (Thu, 02 Mar 2006) | 1 line
- Changed paths:
- D /trunk
- A /ufoai/trunk (from /trunk:165)
-
- # First we start tracking the old revisions:
- GIT_SVN_ID=git-oldsvn git-svn init \
- https://svn.sourceforge.net/svnroot/ufoai/trunk
- GIT_SVN_ID=git-oldsvn git-svn fetch -r1:165
-
- # And now, we continue tracking the new revisions:
- GIT_SVN_ID=git-newsvn git-svn init \
- https://svn.sourceforge.net/svnroot/ufoai/ufoai/trunk
- GIT_SVN_ID=git-newsvn git-svn fetch \
- 166=`git-rev-parse refs/remotes/git-oldsvn`
-------------------------------------------------------------------------
+------------------------------------------------
+ git-svn fetch --follow-parent
+------------------------------------------------
BUGS
----
-If you are not using the SVN::* Perl libraries and somebody commits a
-conflicting changeset to SVN at a bad moment (right before you commit)
-causing a conflict and your commit to fail, your svn working tree
-($GIT_DIR/git-svn/tree) may be dirtied. The easiest thing to do is
-probably just to rm -rf $GIT_DIR/git-svn/tree and run 'rebuild'. You
-can avoid this problem entirely by using 'dcommit'.
-
We ignore all SVN properties except svn:executable. Too difficult to
map them since we rely heavily on git write-tree being _exactly_ the
same on both the SVN and git working trees and I prefer not to clutter
projects / git.git / commitdiff