Tarantool development patches archive
 help / color / mirror / Atom feed
From: Igor Munkin via Tarantool-patches <tarantool-patches@dev.tarantool.org>
To: Sergey Kaplun <skaplun@tarantool.org>,
	Sergey Bronnikov <sergeyb@tarantool.org>
Cc: tarantool-patches@dev.tarantool.org
Subject: Re: [Tarantool-patches] [PATCH luajit] ci: update job concurrency group definition
Date: Thu, 13 Jul 2023 17:06:54 +0000	[thread overview]
Message-ID: <ZLAvLj3PiBLSs0vs@tarantool.org> (raw)
In-Reply-To: <73e2376cd179a89d8be7c0a277e6cab3fecb95bd.1689184997.git.imun@tarantool.org>

Pals, thanks for your reviews!

I've checked the patchset into all long-term branches in
tarantool/luajit and bumped a new version in tarantool/master,
tarantool/release/2.11 and tarantool/release/2.10.

On 12.07.23, Igor Munkin wrote:
> As a result of branch renaming in LuaJIT repository, the existing job
> concurrency group definition rule has become outdated. This patch
> updates the condition according to the new branch naming policy.
> 
> Signed-off-by: Igor Munkin <imun@tarantool.org>
> ---
> 
> Branch: https://github.com/tarantool/luajit/tree/imun/ci-update-job-concurrency-group-def
> 
>  .github/workflows/exotic-builds-testing.yml  | 12 +++++-------
>  .github/workflows/gnumake-builds-testing.yml | 12 +++++-------
>  .github/workflows/lint.yml                   | 12 +++++-------
>  .github/workflows/testing.yml                | 12 +++++-------
>  4 files changed, 20 insertions(+), 28 deletions(-)
> 

<snipped>

> -- 
> 2.30.2
> 

-- 
Best regards,
IM

      parent reply	other threads:[~2023-07-13 17:17 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-07-12 18:06 Igor Munkin via Tarantool-patches
2023-07-13  8:07 ` Sergey Kaplun via Tarantool-patches
2023-07-13  9:58 ` Sergey Bronnikov via Tarantool-patches
2023-07-13 17:06 ` Igor Munkin via Tarantool-patches [this message]

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=ZLAvLj3PiBLSs0vs@tarantool.org \
    --to=tarantool-patches@dev.tarantool.org \
    --cc=imun@tarantool.org \
    --cc=sergeyb@tarantool.org \
    --cc=skaplun@tarantool.org \
    --subject='Re: [Tarantool-patches] [PATCH luajit] ci: update job concurrency group definition' \
    /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