From: Keshav Kini <keshav.kini@gmail.com>
To: git@vger.kernel.org
Cc: Eric Wong <normalperson@yhbt.net>, Keshav Kini <keshav.kini@gmail.com>
Subject: [PATCH] git-svn.txt: mention how to rebuild rev_map files
Date: Mon, 23 Sep 2013 16:19:05 -0500 [thread overview]
Message-ID: <1379971145-8971-1-git-send-email-keshav.kini@gmail.com> (raw)
The man page for `git svn` describes a situation in which "'git svn'
will not be able to rebuild" your .git/svn/**/.rev_map files, but no
mention is made of in what circumstances `git svn` *will* be able to do
so, or how to get `git svn` to do so.
This patch adds some language to the description of the 'fetch' command
to rectify this oversight, and also fixes an AsciiDoc escaping typo.
Signed-off-by: Keshav Kini <keshav.kini@gmail.com>
---
Documentation/git-svn.txt | 11 +++++++----
1 file changed, 7 insertions(+), 4 deletions(-)
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index 4dd3bcb..040117a 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -103,9 +103,12 @@ COMMANDS
'fetch'::
Fetch unfetched revisions from the Subversion remote we are
- tracking. The name of the [svn-remote "..."] section in the
- .git/config file may be specified as an optional command-line
- argument.
+ tracking. If necessary, rebuild the .git/svn/\*\*/.rev_map.*
+ files, given the requisite information exists in commit
+ messages (see the svn.noMetadata config option for more
+ information). The name of the [svn-remote "..."] section in
+ the .git/config file may be specified as an optional
+ command-line argument.
--localtime;;
Store Git commit times in the local timezone instead of UTC. This
@@ -684,7 +687,7 @@ svn-remote.<name>.noMetadata::
+
This option can only be used for one-shot imports as 'git svn'
will not be able to fetch again without metadata. Additionally,
-if you lose your .git/svn/**/.rev_map.* files, 'git svn' will not
+if you lose your .git/svn/\*\*/.rev_map.* files, 'git svn' will not
be able to rebuild them.
+
The 'git svn log' command will not work on repositories using
--
1.8.3.2
next reply other threads:[~2013-09-23 21:20 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-23 21:19 Keshav Kini [this message]
2013-09-25 19:44 ` [PATCH] git-svn.txt: mention how to rebuild rev_map files Jonathan Nieder
2013-09-25 19:47 ` Eric Wong
2013-09-25 23:37 ` Keshav Kini
2013-09-26 0:06 ` Jonathan Nieder
2013-09-26 2:21 ` Keshav Kini
2013-09-26 2:41 ` Keshav Kini
2013-09-29 23:45 ` [PATCH v2 0/4] git-svn.txt: miscellaneous changes Keshav Kini
2013-09-29 23:45 ` [PATCH v2 1/4] git-svn.txt: fix AsciiDoc formatting error Keshav Kini
2013-09-29 23:45 ` [PATCH v2 2/4] git-svn.txt: reword description of gc command Keshav Kini
2013-09-29 23:45 ` [PATCH v2 3/4] git-svn.txt: replace .git with $GIT_DIR Keshav Kini
2013-09-29 23:46 ` [PATCH v2 4/4] git-svn.txt: elaborate on rev_map files Keshav Kini
2013-09-30 19:24 ` [PATCH v2 0/4] git-svn.txt: miscellaneous changes Jonathan Nieder
2013-10-10 6:59 ` Eric Wong
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=1379971145-8971-1-git-send-email-keshav.kini@gmail.com \
--to=keshav.kini@gmail.com \
--cc=git@vger.kernel.org \
--cc=normalperson@yhbt.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.
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).