From: Junio C Hamano <gitster@pobox.com>
To: Mason <slash.tmp@free.fr>
Cc: git <git@vger.kernel.org>
Subject: Re: Salvaging borked project history
Date: Thu, 26 Feb 2015 15:54:11 -0800 [thread overview]
Message-ID: <xmqqlhjkjkkc.fsf@gitster.dls.corp.google.com> (raw)
In-Reply-To: <54EFB0AE.6000600@free.fr> (Mason's message of "Fri, 27 Feb 2015 00:47:58 +0100")
Mason <slash.tmp@free.fr> writes:
>> Mason wrote:
>>
>>> I was planning to write 'git diff -q commit^ commit'
>>> to test for empty commits.
>>
>> s/-q/--quiet/ and all is well, no?
>
> Doh! I've no idea how I missed these...
Yeah, this is one of the unfortunate corners of Git that I can
apologize but cannot do much more than that about (in other words,
making "git diff -q" as a short-hand for "git diff --quiet" is not
acceptable) due to backward compatibility and consistency concerns.
next prev parent reply other threads:[~2015-02-26 23:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-23 17:05 Salvaging borked project history Mason
2015-02-23 19:36 ` Junio C Hamano
2015-02-26 11:54 ` Mason
2015-02-26 18:56 ` Junio C Hamano
2015-02-26 20:25 ` Mason
2015-02-26 21:28 ` Junio C Hamano
2015-02-26 23:47 ` Mason
2015-02-26 23:54 ` Junio C Hamano [this message]
2015-03-04 14:49 ` Mason
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=xmqqlhjkjkkc.fsf@gitster.dls.corp.google.com \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=slash.tmp@free.fr \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.