From: Junio C Hamano <gitster@pobox.com>
To: Alex Vandiver <alex@chmrr.net>
Cc: git <git@vger.kernel.org>
Subject: Re: [PATCH] Reword -M, when in `git log`s documention, to suggest --follow
Date: Sat, 02 Jan 2010 10:43:51 -0800 [thread overview]
Message-ID: <7v1vi8e49k.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: 1262412622-sup-7473@utwig
Alex Vandiver <alex@chmrr.net> writes:
> most common usage model. It seems to me like the more correct fix
> would be to move the diff options to later in the file (after the
> options that are `git log`-specific), or to remove them entirely, and
> replace them with a pointer to git diff's options.
IIRC, the apporach we took earlier that people hated and resulted in the
current "include" approach was to say "It also takes many of options that
diff family of commands take". So reordering may work better but dropping
and referring would not, I suspect.
prev parent reply other threads:[~2010-01-02 18:44 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-21 20:40 [PATCH] Reword -M, when in `git log`s documention, to suggest --follow Alex Vandiver
2010-01-01 0:45 ` Alex Vandiver
2010-01-01 4:35 ` Junio C Hamano
2010-01-02 6:38 ` Alex Vandiver
2010-01-02 18:43 ` Junio C Hamano [this message]
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=7v1vi8e49k.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=alex@chmrr.net \
--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).