From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Undocumented long options
Date: Wed, 20 Dec 2006 17:06:59 +0100 [thread overview]
Message-ID: <200612201707.00346.jnareb@gmail.com> (raw)
Here is the list of undocumented long options I have found in git:
* --abbrev-commit (in revision.c) - I'm not sure _where_ it should
be added, as it afects most visible I think git-log, git-show,
git-rev-list. Implies --abbrev.
* --exclude-existing of git-show-ref; new option
* --reflog of git-show-branch, similar to --no-name and --ahs1-name
options I think; new option
* --timestamp option of git-rev-list. Bit strange, but perhaps useful.
I don't quite know what it does.
* --full-history option of git-rev-list (--full-diff just got
documented). I think it would be nice to have described while at it
git history simplification, and how options like --full-history, path
limiter, --parents interacts with it.
* --trivial option of git-read-tree. It looks like opposite of
(documented) --aggresive option, but source indicates that it might
be not exactly opposite.
* --thin and --no-thin of send-pack. It is plumbing option, but even
plumbing should be documented. Not sure which commands are affected by
this.
--
Jakub Narebski
next reply other threads:[~2006-12-20 16:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-12-20 16:06 Jakub Narebski [this message]
2006-12-20 16:17 ` Undocumented long options Johannes Schindelin
2006-12-20 20:06 ` 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=200612201707.00346.jnareb@gmail.com \
--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