Tarantool development patches archive
 help / color / mirror / Atom feed
From: "Timur Safin" <tsafin@tarantool.org>
To: 'Vladislav Shpilevoy' <v.shpilevoy@tarantool.org>,
	'Cyrill Gorcunov' <gorcunov@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH v1.1] evio: workaround for wsl1 so_linger assertion
Date: Wed, 18 Mar 2020 10:12:04 +0300	[thread overview]
Message-ID: <022d01d5fcf4$884af050$98e0d0f0$@tarantool.org> (raw)
In-Reply-To: <66b262dc-4ca1-2e45-3eed-577662d68b35@tarantool.org>



: -----Original Message-----
: From: Vladislav Shpilevoy <v.shpilevoy@tarantool.org>
: Subject: Re: [PATCH v1.1] evio: workaround for wsl1 so_linger assertion
: 
: > Yup, sorry for the omission, I should automate this somehow
: > (because at the moment there are too many manual steps which are
: > easy to forget or to skip. Do you have any advices/scripts here?)
: 
: Yeah, I use this:
: https://gist.github.com/Gerold103/5471a7ddbeec346c0c845930d5bb9df4
: But it is for bash. Don't know whether you use bash on Windows.

That's quite nice. I'll try to automate it even further (i.e. there is no 
much need to provide manual branch information, and the number of patches
to pick - all them could be automatically calculated), but it's very good
start.  

: > :
: > : > +
: > : >  elseif (${CMAKE_SYSTEM_NAME} STREQUAL "kFreeBSD")
: > : >      set(TARGET_OS_FREEBSD 1)
: > : >      set(TARGET_OS_DEBIAN_FREEBSD 1)
: > : > @@ -19,6 +28,7 @@ elseif (${CMAKE_SYSTEM_NAME} STREQUAL "kFreeBSD")
: > : >      add_definitions("-D_FILE_OFFSET_BITS=64")
: > : >      find_package_message(PLATFORM "Building for Debian/kFreeBSD"
: > : >          "${CMAKE_SYSTEM_NAME}")
: > : > +
: > :
: > : Please, omit not necessary diff. This and other new empty lines
: > : below.
: > :
: >
: > Ok, will remove these unnecessary lines added (though they did
: > add some extra readability to the cmake scripts we have here :) )
: 
: Perhaps, but readability is a subjective thing usually. However
: more important is that such unnecessary diff tends to pollute git
: blame, and pad out patch size making it harder to review.

Ok, ok, will get rid of them in next iteration.

Regards,
Timur

  reply	other threads:[~2020-03-18  7:12 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bb3eef527b48bdd3aacddc27e0597ceedcb84987.1584371177.git.tsafin@tarantool.org>
2020-03-16 16:53 ` Timur Safin
2020-03-16 22:35   ` Vladislav Shpilevoy
2020-03-17 14:40     ` Timur Safin
2020-03-17 21:27       ` Vladislav Shpilevoy
2020-03-18  7:12         ` Timur Safin [this message]
2020-03-19 10:27 ` [Tarantool-patches] [PATCH v1.2] " Timur Safin
2020-03-19 10:52   ` Cyrill Gorcunov
2020-03-19 11:07     ` Timur Safin
2020-03-22 19:21   ` Vladislav Shpilevoy
2020-03-23 23:12     ` 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='022d01d5fcf4$884af050$98e0d0f0$@tarantool.org' \
    --to=tsafin@tarantool.org \
    --cc=gorcunov@tarantool.org \
    --cc=tarantool-patches@dev.tarantool.org \
    --cc=v.shpilevoy@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH v1.1] evio: workaround for wsl1 so_linger assertion' \
    /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