Github messages for voidlinux
 help / color / mirror / Atom feed
From: tibequadorian <tibequadorian@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] ardour: update to 6.6.
Date: Mon, 08 Mar 2021 10:05:32 +0100	[thread overview]
Message-ID: <20210308090532.i-6YpqfCUVtm1msXfwy8f6GdBjCD6_5ZxyxAPQjL2Y4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-29120@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 429 bytes --]

New review comment by tibequadorian on void-packages repository

https://github.com/void-linux/void-packages/pull/29120#discussion_r589265218

Comment:
But they won't retag. From https://tracker.ardour.org/view.php?id=7328:

>git-tag is the very first step in the release procedure. If some issues or regressions are found during the release process, the tag is skipped (e.g. there was no Ardour 5.7 release; 5.7-2 became 5.8)

  parent reply	other threads:[~2021-03-08  9:05 UTC|newest]

Thread overview: 43+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-28 14:45 [PR PATCH] " tibequadorian
2021-02-28 20:42 ` [PR REVIEW] " ericonr
2021-02-28 20:42 ` ericonr
2021-02-28 22:09 ` prez
2021-02-28 22:10 ` prez
2021-03-01  5:48 ` [PR REVIEW] " tibequadorian
2021-03-01  5:49 ` tibequadorian
2021-03-01  5:53 ` [PR PATCH] [Updated] " tibequadorian
2021-03-01  6:07 ` tibequadorian
2021-03-01  6:11 ` [PR PATCH] [Updated] " tibequadorian
2021-03-01 13:08 ` prez
2021-03-01 13:09 ` prez
2021-03-01 13:11 ` tibequadorian
2021-03-01 13:11 ` tibequadorian
2021-03-01 13:12 ` tibequadorian
2021-03-01 13:14 ` prez
2021-03-01 14:33 ` tibequadorian
2021-03-01 14:33 ` [PR PATCH] [Closed]: " tibequadorian
2021-03-01 14:33 ` tibequadorian
2021-03-01 15:51 ` [PR PATCH] [Updated] " tibequadorian
2021-03-01 15:52 ` tibequadorian
2021-03-01 16:00 ` tibequadorian
2021-03-01 16:01 ` [PR PATCH] [Updated] " tibequadorian
2021-03-08  4:12 ` [PR REVIEW] " ericonr
2021-03-08  9:01 ` tibequadorian
2021-03-08  9:04 ` tibequadorian
2021-03-08  9:05 ` tibequadorian [this message]
2021-03-08  9:09 ` tibequadorian
2021-03-08  9:17 ` tibequadorian
2021-03-08  9:44 ` [PR PATCH] [Updated] " tibequadorian
2021-03-08  9:47 ` tibequadorian
2021-03-08  9:54 ` tibequadorian
2021-03-08  9:55 ` [PR REVIEW] " tibequadorian
2021-03-08  9:57 ` [PR PATCH] [Updated] " tibequadorian
2021-03-08 10:01 ` tibequadorian
2021-03-08 10:04 ` [PR REVIEW] " tibequadorian
2021-03-08 10:08 ` tibequadorian
2021-03-08 10:40 ` tibequadorian
2021-03-08 15:38 ` ericonr
2021-03-08 15:40 ` [PR PATCH] [Updated] " tibequadorian
2021-03-08 15:41 ` tibequadorian
2021-03-08 15:56 ` [PR REVIEW] " tibequadorian
2021-03-09  6:36 ` [PR PATCH] [Merged]: " ericonr

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=20210308090532.i-6YpqfCUVtm1msXfwy8f6GdBjCD6_5ZxyxAPQjL2Y4@z \
    --to=tibequadorian@users.noreply.github.com \
    --cc=ml@inbox.vuxu.org \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).