Tarantool development patches archive
 help / color / mirror / Atom feed
From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
To: Serge Petrenko <sergepetrenko@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 1/1] iproto: show real port in logs and box.info.listen
Date: Wed, 18 Mar 2020 23:38:32 +0100	[thread overview]
Message-ID: <9ba81bc4-9ea3-65bd-41c2-924c1fb99881@tarantool.org> (raw)
In-Reply-To: <27C6CB53-B660-4195-A09F-9B58EA089501@tarantool.org>

Thanks for the review!

On 18/03/2020 19:18, Serge Petrenko wrote:
> Hi! Thanks for the patch!
> Alexander asked me to do the 2nd review.
> 
> The patch LGTM.
> 
> Sorry for nitpicking,  but looks like your changelog request has a typo in it:
>> @ChangeLog
>> - box.info.listen - new record in box.info <http://box.info>, which shows a
>>  real port when bound to port 0. For example, if box.cfg
>>  'listen' parameter was set to '127.0.0.1:0', box.info.listen
>>  will show '127.0.0.1:<real port > 0>' (gh-4620).
> just <real port>, without 0>, right?

Nope, I meant > 0. I wanted to emphasize, that the port is never
shown as 0 anymore. It is always some real port > 0.

  reply	other threads:[~2020-03-18 22:38 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-12 22:03 Vladislav Shpilevoy
2019-11-13  0:32 ` Vladislav Shpilevoy
2019-11-13 22:31 ` Vladislav Shpilevoy
2020-02-21 19:51 ` Sergey Ostanevich
2020-02-22  8:34   ` Sergey Ostanevich
2020-02-22 14:47     ` Vladislav Shpilevoy
2020-02-22 15:00   ` Vladislav Shpilevoy
2020-03-03 13:26     ` Sergey Ostanevich
2020-02-22 15:00 ` Vladislav Shpilevoy
2020-03-18 18:18 ` Serge Petrenko
2020-03-18 22:38   ` Vladislav Shpilevoy [this message]
2020-03-19 10:24     ` Serge Petrenko
2020-03-19 10:45 ` Kirill Yukhin

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=9ba81bc4-9ea3-65bd-41c2-924c1fb99881@tarantool.org \
    --to=v.shpilevoy@tarantool.org \
    --cc=sergepetrenko@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH 1/1] iproto: show real port in logs and box.info.listen' \
    /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

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox