Tarantool development patches archive
 help / color / mirror / Atom feed
From: "Ivan Koptelov" <ivan.koptelov@tarantool.org>
To: tarantool-patches@freelists.org
Cc: "Nikita Pettik" <korablev@tarantool.org>
Subject: [tarantool-patches] [tarantool-patches] Re: [PATCH] sql: Fixes op-codes' generation for skip-scan
Date: Fri, 04 May 2018 11:10:05 +0300	[thread overview]
Message-ID: <1525421405.73000074@f511.i.mail.ru> (raw)
In-Reply-To: <A2F7D746-8C03-42E1-A2D6-708D23B23F76@tarantool.org>


[-- Attachment #1.1: Type: text/plain, Size: 963 bytes --]


>Hello. Do not start commit subject with capital letter after ‘:’.
Fixed.
>Also, I don’t see your branch at remote repository:
>you should push it before sending patch
>(in order to check Travis status, at least). 
Pushed.  https://github.com/tarantool/tarantool/tree/sb/scip-scan-fix  
>The limit for commit message is 72 chars…
>Just reminding you. 
I am confused. 72 chars is a limit for the whole commit
message? 
>Just enumerate with comma:
>Closes #xxxx, #xxxx 
Ok.
>Put here link to the branch and link to the issue 
Ok.
>Make sure that code fits into 80 chars. Now I can’t check it,
>since you haven’t pushed your branch.
I am confused again. What is this 80-chars constraint about?
>I would add to the name of test number of issue:
>gh-xxxx-skip-scan.test.lua
>
>Or, if it covers several issues, put comments before
>test cases indicating number of issue it belongs to. 
Fxd.
>Consider formatting of curly braces.
Fxd.

-- 
Ivan Koptelov

[-- Attachment #1.2: Type: text/html, Size: 6080 bytes --]

[-- Attachment #2: 0001-sql-fixes-op-codes-generation-for-skip-scan.patch --]
[-- Type: application/x-patch, Size: 5600 bytes --]

  reply	other threads:[~2018-05-04  8:10 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-04-27 10:06 [tarantool-patches] " Ivan Koptelov
2018-04-27 11:01 ` [tarantool-patches] " n.pettik
2018-05-04  8:10   ` Ivan Koptelov [this message]
2018-05-04  9:50     ` n.pettik
2018-05-07 10:42       ` Ivan Koptelov
2018-05-08 16:59         ` n.pettik
2018-05-11  5:28           ` 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=1525421405.73000074@f511.i.mail.ru \
    --to=ivan.koptelov@tarantool.org \
    --cc=korablev@tarantool.org \
    --cc=tarantool-patches@freelists.org \
    --subject='[tarantool-patches] [tarantool-patches] Re: [PATCH] sql: Fixes op-codes'\'' generation for skip-scan' \
    /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