From: Andrew Ruder <andy@aeruder.net>
To: Junio C Hamano <junkio@cox.net>
Cc: git@vger.kernel.org
Subject: [PATCH] Update git-am documentation
Date: Mon, 16 Apr 2007 07:47:31 -0500 [thread overview]
Message-ID: <20070416124731.GA23429@localdomain> (raw)
In-Reply-To: <7vy7ksvjxt.fsf@assigned-by-dhcp.cox.net>
Documentation/git-am.txt missing several short versions
of options.
Signed-off-by: Andrew Ruder <andy@aeruder.net>
---
Ah, I misunderstood your first reply. If this is truly only for
internal usage, it should definitely not be in the manpage as
abuse *will* occur. :) Let's just hope that nobody finds this thread
via the mailing list archives.
Documentation/git-am.txt | 18 +++++++++---------
1 files changed, 9 insertions(+), 9 deletions(-)
diff --git a/Documentation/git-am.txt b/Documentation/git-am.txt
index 148ce40..759e3a5 100644
--- a/Documentation/git-am.txt
+++ b/Documentation/git-am.txt
@@ -26,18 +26,18 @@ OPTIONS
The list of mailbox files to read patches from. If you do not
supply this argument, reads from the standard input.
---signoff::
+-s, --signoff::
Add `Signed-off-by:` line to the commit message, using
the committer identity of yourself.
---dotest=<dir>::
+-d=<dir>, --dotest=<dir>::
Instead of `.dotest` directory, use <dir> as a working
area to store extracted patches.
---keep::
+-k, --keep::
Pass `-k` flag to `git-mailinfo` (see gitlink:git-mailinfo[1]).
---utf8::
+-u, --utf8::
Pass `-u` flag to `git-mailinfo` (see gitlink:git-mailinfo[1]).
The proposed commit log message taken from the e-mail
are re-coded into UTF-8 encoding (configuration variable
@@ -48,14 +48,14 @@ This was optional in prior versions of git, but now it is the
default. You could use `--no-utf8` to override this.
--no-utf8::
- Do not pass `-u` flag to `git-mailinfo` (see
+ Pass `-n` flag to `git-mailinfo` (see
gitlink:git-mailinfo[1]).
---binary::
+-b, --binary::
Pass `--allow-binary-replacement` flag to `git-apply`
(see gitlink:git-apply[1]).
---3way::
+-3, --3way::
When the patch does not apply cleanly, fall back on
3-way merge, if the patch records the identity of blobs
it is supposed to apply to, and we have those blobs
@@ -73,10 +73,10 @@ default. You could use `--no-utf8` to override this.
These flags are passed to the `git-apply` program that applies
the patch.
---interactive::
+-i, --interactive::
Run interactively, just like git-applymbox.
---resolved::
+-r, --resolved::
After a patch failure (e.g. attempting to apply
conflicting patch), the user has applied it by hand and
the index file stores the result of the application.
--
1.5.1.1.98.gedb4f-dirty
next prev parent reply other threads:[~2007-04-16 12:47 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-04-16 5:35 [PATCH] Add policy on user-interface changes Andrew Ruder
2007-04-16 6:20 ` [PATCH] Update git-am documentation Andrew Ruder
2007-04-16 6:56 ` Junio C Hamano
2007-04-16 7:21 ` Andrew Ruder
2007-04-16 7:48 ` Junio C Hamano
2007-04-16 12:47 ` Andrew Ruder [this message]
2007-04-16 6:20 ` [PATCH] Update git-applymbox documentation Andrew Ruder
2007-04-16 6:40 ` Andrew Ruder
2007-04-16 6:20 ` [PATCH] Update git-annotate/git-blame documentation Andrew Ruder
2007-04-16 7:24 ` Alex Riesen
2007-04-16 7:26 ` Andrew Ruder
2007-04-16 7:52 ` Junio C Hamano
2007-04-17 2:45 ` Andrew Ruder
2007-04-16 6:20 ` [PATCH] Update git-apply documentation Andrew Ruder
2007-04-19 3:03 ` [PATCH] Update git-archive documentation Andrew Ruder
2007-04-19 3:03 ` [PATCH] Update git-cherry-pick documentation Andrew Ruder
2007-04-19 3:03 ` [PATCH] Fix unmatched emphasis tag in git-tutorial Andrew Ruder
2007-04-19 3:03 ` [PATCH] Update git-config documentation Andrew Ruder
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=20070416124731.GA23429@localdomain \
--to=andy@aeruder.net \
--cc=git@vger.kernel.org \
--cc=junkio@cox.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).