From: Yann Dirson <ydirson@altern.org>
To: git@vger.kernel.org
Cc: Yann Dirson <ydirson@altern.org>
Subject: [PATCH 1/2] git-svn: add some in-code documentation (options-related).
Date: Mon, 22 Jun 2009 00:48:40 +0200 [thread overview]
Message-ID: <1245624521-30769-2-git-send-email-ydirson@altern.org> (raw)
In-Reply-To: <1245624521-30769-1-git-send-email-ydirson@altern.org>
Signed-off-by: Yann Dirson <ydirson@altern.org>
---
git-svn.perl | 8 ++++++++
1 files changed, 8 insertions(+), 0 deletions(-)
diff --git a/git-svn.perl b/git-svn.perl
index 3301797..e2d5eff 100755
--- a/git-svn.perl
+++ b/git-svn.perl
@@ -71,6 +71,13 @@ my ($_stdin, $_help, $_edit,
$_git_format, $_commit_url, $_tag);
$Git::SVN::_follow_parent = 1;
$_q ||= 0;
+
+# Option structures here are used to define both command-line options
+# and git-config keys. They are handled by read-repo-config().
+# Options in mixed case and with only a long form are only for the
+# config file. All options available from command-line are available
+# as config-file options too, but without any dash in their names.
+
my %remote_opts = ( 'username=s' => \$Git::SVN::Prompt::_username,
'config-dir=s' => \$Git::SVN::Ra::config_dir,
'no-auth-cache' => \$Git::SVN::Prompt::_no_auth_cache,
@@ -184,6 +191,7 @@ my %cmd = (
'show-commit' => \$Git::SVN::Log::show_commit,
'non-recursive' => \$Git::SVN::Log::non_recursive,
'authors-file|A=s' => \$_authors,
+ # FIXME: lacks authors-prog ?
'color' => \$Git::SVN::Log::color,
'pager=s' => \$Git::SVN::Log::pager
} ],
--
1.6.3.1
next prev parent reply other threads:[~2009-06-21 22:49 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-17 20:18 Improving git-svn documentation Yann Dirson
2009-06-17 22:04 ` Marc Branchaud
2009-06-21 22:48 ` [WIP PATCH 0/2] Some documentation improvements for git-svn Yann Dirson
2009-06-21 22:48 ` Yann Dirson [this message]
2009-06-21 22:48 ` [PATCH 2/2] git-svn user documentation update Yann Dirson
2009-06-21 23:48 ` [PATCH 1/2] git-svn: add some in-code documentation (options-related) Junio C Hamano
2009-06-22 19:12 ` Yann Dirson
2009-06-25 8:47 ` Improving git-svn documentation 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=1245624521-30769-2-git-send-email-ydirson@altern.org \
--to=ydirson@altern.org \
--cc=git@vger.kernel.org \
/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).