From: Sergey Organov <sorganov@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [BUG] Documentation: git log: --exit-code undocumented?
Date: Mon, 01 Dec 2014 19:43:24 +0300 [thread overview]
Message-ID: <87oarngw2b.fsf@osv.gnss.ru> (raw)
In-Reply-To: <xmqqa937qqb7.fsf@gitster.dls.corp.google.com> (Junio C. Hamano's message of "Mon, 01 Dec 2014 08:37:32 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> Sergey Organov <sorganov@gmail.com> writes:
>
>> Junio C Hamano <gitster@pobox.com> writes:
>>
>>> Sergey Organov <sorganov@gmail.com> writes:
>>>
>>>> Hello,
>>>>
>>>> $ git help log | grep exit-code
>>>> problems are found. Not compatible with --exit-code.
>>>> $
>>>>
>>>> What --exit-code does in "git log"?
>>>
>>> It doesn't. That is why it is not listed.
>>
>> Then, how can --check possibly interfer with it?
>
> The description is shared with "git diff" and friends, which is
> invoked via "git log -p". As "log" does not give the exit code
> of individual "diff-tree" invocation for each commit, --exit-code
> option is irrelevant.
Do you agree there is some minor problem here? First, "git log"
silently eats the --exit-code option that does nothing. Next, git-log
manual page doesn't include --exit-log description while refers to it
elsewhere. What's proposed resulution?
--
Sergey.
next prev parent reply other threads:[~2014-12-01 16:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-01 11:50 [BUG] Documentation: git log: --exit-code undocumented? Sergey Organov
2014-12-01 16:29 ` Junio C Hamano
2014-12-01 16:32 ` Sergey Organov
2014-12-01 16:37 ` Junio C Hamano
2014-12-01 16:43 ` Sergey Organov [this message]
2014-12-01 17:32 ` David Kastrup
2014-12-01 17:49 ` Junio C Hamano
2014-12-01 18:30 ` David Kastrup
2014-12-02 11:30 ` Sergey Organov
2014-12-02 12:27 ` John Keeping
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=87oarngw2b.fsf@osv.gnss.ru \
--to=sorganov@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
/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.