From: apenwarr@gmail.com
To: git@vger.kernel.org
Cc: Avery Pennarun <apenwarr@versabanq.com>,
Avery Pennarun <apenwarr@gmail.com>
Subject: [PATCH 3/3] git-svn: add documentation for --add-author-from option.
Date: Tue, 15 Apr 2008 21:04:18 -0400 [thread overview]
Message-ID: <1208307858-31039-3-git-send-email-apenwarr@gmail.com> (raw)
In-Reply-To: <1208307858-31039-2-git-send-email-apenwarr@gmail.com>
From: Avery Pennarun <apenwarr@versabanq.com>
Signed-off-by: Avery Pennarun <apenwarr@gmail.com>
---
Documentation/git-svn.txt | 6 ++++++
1 files changed, 6 insertions(+), 0 deletions(-)
diff --git a/Documentation/git-svn.txt b/Documentation/git-svn.txt
index 4ad567a..acd77eb 100644
--- a/Documentation/git-svn.txt
+++ b/Documentation/git-svn.txt
@@ -65,6 +65,12 @@ COMMANDS
When retrieving svn commits into git (as part of fetch, rebase, or
dcommit operations), look for the first From: or Signed-off-by: line
in the log message and use that as the author string.
+--add-author-from;;
+ When committing to svn from git (as part of commit or dcommit
+ operations), if the existing log message doesn't already have a
+ From: or Signed-off-by: line, append a From: line based on the
+ git commit's author string. If you use this, then --use-log-author
+ will retrieve a valid author string for all commits.
--username=<USER>;;
For transports that SVN handles authentication for (http,
https, and plain svn), specify the username. For other
--
1.5.4.3
next prev parent reply other threads:[~2008-04-16 1:20 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-04-16 1:04 [PATCH 1/3] git-svn: add documentation for --use-log-author option apenwarr
2008-04-16 1:04 ` [PATCH 2/3] git-svn: Add --add-author-from option apenwarr
2008-04-16 1:04 ` apenwarr [this message]
2008-04-16 4:33 ` Junio C Hamano
2008-04-16 16:46 ` Avery Pennarun
2008-04-16 18:36 ` Junio C Hamano
2008-04-16 18:45 ` Avery Pennarun
2008-04-16 19:11 ` Richard Quirk
2008-04-16 19:23 ` Dmitry Potapov
2008-04-16 22:24 ` Sam Vilain
2008-04-16 22:34 ` Avery Pennarun
2008-04-17 4:36 ` 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=1208307858-31039-3-git-send-email-apenwarr@gmail.com \
--to=apenwarr@gmail.com \
--cc=apenwarr@versabanq.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.