From: Michael J Gruber <git@drmicha.warpmail.net>
To: git@vger.kernel.org
Cc: Junio C Hamano <gitster@pobox.com>, Jeff King <peff@peff.net>
Subject: [PATCHv2 0/3] add/commit -u/-a/-A
Date: Sun, 27 Feb 2011 16:50:09 +0100 [thread overview]
Message-ID: <cover.1298821535.git.git@drmicha.warpmail.net> (raw)
In-Reply-To: <4D68D630.9000608@drmicha.warpmail.net>
v2 takes "all-tracked" as the long form of "-a" for add and commit.
I would think that "changes from all tracked files" would include the special
change "deletion", but I'm open to making the description more verbous.
But as a general rule, "git cmd -h" output should serve as a reminder,
distinguishing the options from each other, not as complete description.
Michael J Gruber (3):
git-add: make -A description clearer vs. -u
git-commit: rename --all to --all-tracked
git-add: rename -u to -a
Documentation/git-add.txt | 8 ++++----
Documentation/git-commit.txt | 2 +-
Documentation/git-rm.txt | 2 +-
Documentation/gitattributes.txt | 4 ++--
builtin/add.c | 7 ++++---
builtin/commit.c | 12 ++++++------
t/t1511-rev-parse-caret.sh | 2 +-
t/t2200-add-update.sh | 26 +++++++++++++-------------
t/t2201-add-update-typechange.sh | 6 +++---
t/t2203-add-intent.sh | 2 +-
t/t3030-merge-recursive.sh | 2 +-
t/t3415-rebase-autosquash.sh | 16 ++++++++--------
t/t4037-diff-r-t-dirs.sh | 2 +-
t/t6022-merge-rename.sh | 2 +-
t/t6036-recursive-corner-cases.sh | 2 +-
15 files changed, 48 insertions(+), 47 deletions(-)
--
1.7.4.1.224.gefc87
next prev parent reply other threads:[~2011-02-27 15:49 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-25 14:45 [PATCH/RFC 0/3] add/commit -u/-a/-A Michael J Gruber
2011-02-25 14:45 ` [PATCH/RFC 1/3] git-add: make -A description clearer vs. -u Michael J Gruber
2011-02-25 19:04 ` Junio C Hamano
2011-02-25 14:45 ` [PATCH/RFC 2/3] git-commit: rename --all to --track Michael J Gruber
2011-02-25 19:08 ` Junio C Hamano
2011-02-25 14:45 ` [PATCH/RFC 3/3] git-add: rename -u to -a Michael J Gruber
2011-02-25 19:40 ` Junio C Hamano
[not found] ` <7vr5aw9b7m.fsf@alter.siamese.dyndns.org>
2011-02-26 10:30 ` [PATCH/RFC 0/3] add/commit -u/-a/-A Michael J Gruber
2011-02-27 15:50 ` Michael J Gruber [this message]
2011-02-27 15:50 ` [PATCHv2 1/3] git-add: make -A description clearer vs. -u Michael J Gruber
2011-02-27 23:35 ` Junio C Hamano
2011-02-27 15:50 ` [PATCHv2 2/3] git-commit: rename --all to --all-tracked Michael J Gruber
2011-02-27 15:50 ` [PATCHv2 3/3] git-add: rename -u to -a Michael J Gruber
2011-02-27 16:38 ` Nguyen Thai Ngoc Duy
2011-02-28 6:40 ` Junio C Hamano
2011-02-28 8:30 ` Michael J Gruber
2011-02-28 8:42 ` Miles Bader
2011-02-28 8:46 ` Michael J Gruber
2011-02-28 8:53 ` Miles Bader
2011-02-28 9:05 ` Snipping on this list (Was: Re: [PATCHv2 3/3] git-add: rename -u to -a) Michael J Gruber
2011-02-28 18:18 ` Snipping on this list Junio C Hamano
2011-02-28 9:03 ` [PATCHv2 3/3] git-add: rename -u to -a Miles Bader
2011-02-28 9:08 ` Michael J Gruber
2011-02-28 9:40 ` Matthieu Moy
2011-02-28 9:49 ` Michael J Gruber
2011-02-28 10:01 ` Tor Arntsen
2011-02-28 10:03 ` Michael J Gruber
2011-02-28 10:05 ` Matthieu Moy
2011-02-28 10:53 ` Michael J Gruber
2011-02-28 18:21 ` Junio C Hamano
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=cover.1298821535.git.git@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=peff@peff.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).