Tarantool development patches archive
 help / color / mirror / Atom feed
From: Kirill Yukhin <kyukhin@tarantool.org>
To: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH 5/5] Apply Clang formatter
Date: Wed, 11 Nov 2020 08:23:37 +0000	[thread overview]
Message-ID: <20201111082337.65cqw4rtrru5xhmo@tarantool.org> (raw)
In-Reply-To: <a52ef5b1-aca3-8bf7-7f06-4e8cb12ce769@tarantool.org>

Hello,

On 10 Nov 21:38, Vladislav Shpilevoy wrote:
> > On 02 Nov 22:05, Vladislav Shpilevoy wrote:
> >> Ok. I will review the whole patch, every single line. Don't push
> >> it beforehand then.
> > 
> > In my previous e-mail I've explicitly stated that current formatter
> > is not suitable for us. Quote:
> > 
> >>> After all, having p.3 and p.8 unresolved I guess we cannot proceed
> >>> without changes to formatter.
> > 
> > Please, see what does it mean here [1].
> > 
> > [1] - https://translate.google.com/#view=home&op=translate&sl=auto&tl=ru&text=After%20all%2C%20having%20p.3%20and%20p.8%20unresolved%20I%20guess%20we%20cannot%20proceed%20without%20changes%20to%20formatter.
> 
> Ok, lets play quotes. Here is yours:
> 
> 	I am not sure. Anyway I think this is not a blocker for having fully automated
> 	code formatting.
> 
> Talking of this quote:
> 
> 	After all, having p.3 and p.8 unresolved I guess we cannot proceed
> 	without changes to formatter.
> 
> It is not the same as saying that we won't use the formatter. You just said,
> you will try to fix review points 3 and 8. Which were not even the worst.
> Which leads to the point you are ok with the other issues. Tons of
> other issues, as I found in the detailed review. And I am not ok with these
> issues.

You understood completely correct. To the moment we cannot use Clang formatter
since it has unresolvable flaws (in p.3 and p.8). But that doesn't mean we
won't use one of code checkers if found them suitable or if Clang formatter
will become better.
Thanks for sharing your `not ok`, all wyou contributions seems very valuable,
however this doesn't seem to be a blocker.

--
Regards, Kirill Yukhin

  reply	other threads:[~2020-11-11  8:23 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-30 11:43 [Tarantool-patches] [PATCH 0/5] Add clang format Kirill Yukhin
2020-10-30 11:43 ` [Tarantool-patches] [PATCH 1/5] clang-format: guard various declarations Kirill Yukhin
2020-11-08 15:09   ` Vladislav Shpilevoy
2020-10-30 11:43 ` [Tarantool-patches] [PATCH 2/5] Add .clang-format for src/box/ Kirill Yukhin
2020-10-30 11:43 ` [Tarantool-patches] [PATCH 3/5] build: add clang-format rules Kirill Yukhin
2020-11-08 15:09   ` Vladislav Shpilevoy
2020-10-30 11:43 ` [Tarantool-patches] [PATCH 4/5] gitlab-ci: add code style check Kirill Yukhin
2020-10-30 11:43 ` [Tarantool-patches] [PATCH 5/5] Apply Clang formatter Kirill Yukhin
2020-10-30 13:42   ` Konstantin Osipov
2020-10-30 23:04   ` Vladislav Shpilevoy
2020-11-01 21:40     ` Konstantin Osipov
2020-11-02  7:35     ` Kirill Yukhin
2020-11-02 21:05       ` Vladislav Shpilevoy
2020-11-10 14:16         ` Kirill Yukhin
2020-11-10 20:38           ` Vladislav Shpilevoy
2020-11-11  8:23             ` Kirill Yukhin [this message]
2020-11-08 15:11   ` Vladislav Shpilevoy

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=20201111082337.65cqw4rtrru5xhmo@tarantool.org \
    --to=kyukhin@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH 5/5] Apply Clang formatter' \
    /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