From: Junio C Hamano <gitster@pobox.com>
To: VMiklos <vmiklos@frugalware.org>
Cc: git@vger.kernel.org
Subject: Re: git log vs git diff vs --name-status
Date: Thu, 23 Aug 2007 02:33:38 -0700 [thread overview]
Message-ID: <7vr6lutx1p.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <20070823084512.GB31174@genesis.frugalware.org> (vmiklos@frugalware.org's message of "Thu, 23 Aug 2007 10:45:12 +0200")
VMiklos <vmiklos@frugalware.org> writes:
> Na Thu, Aug 23, 2007 at 10:43:15AM +0200, VMiklos <vmiklos@frugalware.org> pisal(a):
>> M dir
>
> sorry, i needed the -r option
I know.
I've been debating myself if --name-status should imply -r
(recursive behaviour) for "git log". More specifically, I think
a reasonable guiding principles would be something like:
* Anything that looks at the file contents level change (that
is, -p, --stat and --numstat) should always imply recursive;
* Anything that is Porcelain should always imply recursive.
I am fairly certain about the first one, but not absolutely sure
about the latter. The first principle does not justify making
your example to recurse, but the second, if we accept it, would.
next prev parent reply other threads:[~2007-08-23 9:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-23 8:43 git log vs git diff vs --name-status VMiklos
2007-08-23 8:45 ` VMiklos
2007-08-23 9:33 ` Junio C Hamano [this message]
2007-08-24 8:58 ` VMiklos
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=7vr6lutx1p.fsf@gitster.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=vmiklos@frugalware.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).