From: Eric Sunshine <sunshine@sunshineco.com>
To: Koosha Khajehmoogahi <koosha@posteo.de>
Cc: Git List <git@vger.kernel.org>, Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH v3 3/5] Documentation: add git-log --merges= option and log.merges config. var
Date: Thu, 16 Apr 2015 00:49:15 -0400 [thread overview]
Message-ID: <CAPig+cS7aCN5Boevnp_S+rgJP4GKxpMeVSnjEaWEKcNECC-21A@mail.gmail.com> (raw)
In-Reply-To: <552EE5D7.9070703@posteo.de>
On Wed, Apr 15, 2015 at 6:27 PM, Koosha Khajehmoogahi <koosha@posteo.de> wrote:
> On 04/14/2015 08:42 AM, Eric Sunshine wrote:
>> On Mon, Apr 13, 2015 at 11:29 AM, Koosha Khajehmoogahi <koosha@posteo.de> wrote:
>>> From: Junio C Hamano <gitster@pobox.com>
>>>
>>> [kk: added documentation in git-log.txt]
>>>
>>> Signed-off-by: Koosha Khajehmoogahi <koosha@posteo.de>
>>> ---
>>> @@ -96,6 +96,23 @@ if it is part of the log message.
>>> --remove-empty::
>>> Stop when a given path disappears from the tree.
>>>
>>> +--merges={show|hide|only}::
>>> +
>>> + Limit the output by type of commits.
>>> +
>>> + `hide`;;
>>> + Hide merge commits from the output.
>>> +
>>> + `only`;;
>>> + Hide non-merge commits from the output (i.e showing
>>> + only merge commits).
>>> +
>>> + `show`;;
>>> + Do not hide either merge or non-merge commits. This
>>> + is primarily useful when the user has non-standard
>>> + setting of `log.merges` configuration variable that
>>> + needs to be overriden from the command line.
>>
>> s/overriden/overridden/
>
> Should I send a new reroll or wait for reviews on my other commits.
> I have not received any review on other patches of this series yet.
Lack of review comments does not necessarily mean that people did not
review the patches; it could mean that reviewers had nothing more to
say. In addition to pointing out the typo above, I also made a small
comment[1] on patch 4/5, but otherwise did not find anything else
about which to comment.
Whether or not you should re-send is something Junio can answer. He
will sometimes silently pick up a series as-is or sometimes silently
make minor fixes based upon review comments. Check his 'pu' branch
periodically to see if your series appears there and if it has those
minor adjustments. If not, and if he doesn't answer this question,
then you may need to re-roll.
[1]: http://article.gmane.org/gmane.comp.version-control.git/267118
next prev parent reply other threads:[~2015-04-16 4:49 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-13 15:29 [PATCH v3 1/5] revision: add --merges={show|only|hide} option Koosha Khajehmoogahi
2015-04-13 15:29 ` [PATCH v3 2/5] log: honor log.merges= option Koosha Khajehmoogahi
2015-04-16 6:07 ` Junio C Hamano
2015-04-13 15:29 ` [PATCH v3 3/5] Documentation: add git-log --merges= option and log.merges config. var Koosha Khajehmoogahi
2015-04-14 6:42 ` Eric Sunshine
2015-04-15 22:27 ` Koosha Khajehmoogahi
2015-04-16 4:49 ` Eric Sunshine [this message]
2015-04-13 15:29 ` [PATCH v3 4/5] t4202-log: add tests for --merges= Koosha Khajehmoogahi
2015-04-14 6:52 ` Eric Sunshine
2015-04-13 15:29 ` [PATCH v3 5/5] bash-completion: add support for git-log --merges= and log.merges Koosha Khajehmoogahi
2015-04-21 12:51 ` [PATCH] squash! " SZEDER Gábor
2015-04-21 17:42 ` 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=CAPig+cS7aCN5Boevnp_S+rgJP4GKxpMeVSnjEaWEKcNECC-21A@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=koosha@posteo.de \
/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).