From: jidanni@jidanni.org
To: git@vger.kernel.org
Subject: [PATCH/RFC] Documentation/git-mailsplit.txt: Emphasize -o more
Date: Tue, 13 Jan 2009 05:28:55 +0800 [thread overview]
Message-ID: <877i50jjs8.fsf@jidanni.org> (raw)
The need for -o cannot be overstated. Else the arguments get
interpreted differently. We also mention the output.
(By the way, "fatal: unknown option: -o" is seen if a space comes
after it.)
Signed-off-by: jidanni <jidanni@jidanni.org>
---
Documentation/git-mailsplit.txt | 11 ++++++++---
1 files changed, 8 insertions(+), 3 deletions(-)
diff --git a/Documentation/git-mailsplit.txt b/Documentation/git-mailsplit.txt
index 5cc94ec..5dc24c9 100644
--- a/Documentation/git-mailsplit.txt
+++ b/Documentation/git-mailsplit.txt
@@ -13,10 +13,18 @@ DESCRIPTION
-----------
Splits a mbox file or a Maildir into a list of files: "0001" "0002" .. in the
specified directory so you can process them further from there.
+The number of files produced is printed to the standard output.
IMPORTANT: Maildir splitting relies upon filenames being sorted to output
patches in the correct order.
+REQUIRED OPTIONS
+-------
+-o<directory>::
+ Directory in which to place the individual messages.
+ -o is required or else arguments may be misinterpreted in a
+ backwards compatibility mode.
+
OPTIONS
-------
<mbox>::
@@ -27,9 +35,6 @@ OPTIONS
Root of the Maildir to split. This directory should contain the cur, tmp
and new subdirectories.
--o<directory>::
- Directory in which to place the individual messages.
-
-b::
If any file doesn't begin with a From line, assume it is a
single mail message instead of signaling error.
--
1.6.0.6
next reply other threads:[~2009-01-12 21:30 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-12 21:28 jidanni [this message]
2009-01-12 22:06 ` [PATCH/RFC] Documentation/git-mailsplit.txt: Emphasize -o more Junio C Hamano
2009-01-12 22:55 ` jidanni
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=877i50jjs8.fsf@jidanni.org \
--to=jidanni@jidanni.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 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.