From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: git-am vs. git-applymbox
Date: Sun, 05 Nov 2006 13:10:28 +0100 [thread overview]
Message-ID: <eikkaq$au7$1@sea.gmane.org> (raw)
git-applymbox - Apply a series of patches in a mailbox
git-am - Apply a series of patches in a mailbox
What are the differences between thos two commands, UI-wise and capability
(feature) wise? Which one should I use? Which one do _you_ use?
And why git has yet another set of commands which do the same (well,
git-annotate vs. git-blame "war" was won by git-blame, and git-pickaxe was
born).
By the way, could we standarize somewhat short options for git commands,
like -q for quiet, -v for verbose, -i for interactive, -S for pickaxe
(search in diff), -n for some kind of no-op/do nothing (e.g. --no-commit),
-f for force, -l for list, -k for skip errors/keep working even in the case
of errors? It would be nice to have this in Documentation/API somewhere...
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next reply other threads:[~2006-11-05 12:10 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-05 12:10 Jakub Narebski [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-11-05 21:42 git-am vs. git-applymbox linux
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='eikkaq$au7$1@sea.gmane.org' \
--to=jnareb@gmail.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 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).