From: Stefan Sperling <stsp@elego.de>
To: git@vger.kernel.org
Cc: subversion@elego.de
Subject: [PATCH] Document -u option in git-svnimport man page
Date: Tue, 21 Aug 2007 19:15:09 +0200 [thread overview]
Message-ID: <20070821171509.GB1721@jack.stsp.lan> (raw)
[-- Attachment #1: Type: text/plain, Size: 929 bytes --]
diff --git a/Documentation/git-svnimport.txt b/Documentation/git-svnimport.txt
index 2cfc407..c9c8c5d 100644
--- a/Documentation/git-svnimport.txt
+++ b/Documentation/git-svnimport.txt
@@ -65,6 +65,9 @@ When importing incrementally, you might need to edit the .git/svn2git file.
Prepend 'rX: ' to commit messages, where X is the imported
subversion revision.
+-u::
+ Replace underscores in tag names with periods.
+
-I <ignorefile_name>::
Import the svn:ignore directory property to files with this
name in each directory. (The Subversion and GIT ignore
--
Stefan Sperling <stsp@elego.de> Software Developer
elego Software Solutions GmbH HRB 77719
Gustav-Meyer-Allee 25, Gebaeude 12 Tel: +49 30 23 45 86 96
13355 Berlin Fax: +49 30 23 45 86 95
http://www.elego.de Geschaeftsfuehrer: Olaf Wagner
[-- Attachment #2: Type: application/pgp-signature, Size: 187 bytes --]
reply other threads:[~2007-08-21 17:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20070821171509.GB1721@jack.stsp.lan \
--to=stsp@elego.de \
--cc=git@vger.kernel.org \
--cc=subversion@elego.de \
/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).