Github messages for voidlinux
 help / color / mirror / Atom feed
From: Eluminae <Eluminae@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] WIP: ctags: update to 5.9.20210214.0
Date: Fri, 19 Feb 2021 22:47:57 +0100	[thread overview]
Message-ID: <20210219214757.qhbLCzU3iWtCoRjy7e_x_cbiBrUeeS0xTw6nDItcXqw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-28885@inbox.vuxu.org>

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

New review comment by Eluminae on void-packages repository

https://github.com/void-linux/void-packages/pull/28885#discussion_r579494412

Comment:
> You can do autogen.sh in pre_configure, which is preferred.
understood

> This depends on the resolution to #28544 (comment)

So are we trying to disable checks ? all checks ? or add a patch to disable some specifcs checks ?

Or maybe I'm not aware of enough github issues discussions :D

  parent reply	other threads:[~2021-02-19 21:47 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-19 16:01 [PR PATCH] " Eluminae
2021-02-19 16:16 ` [PR PATCH] [Updated] " Eluminae
2021-02-19 16:17 ` Eluminae
2021-02-19 16:21 ` Eluminae
2021-02-19 16:26 ` Eluminae
2021-02-19 16:56 ` [PR PATCH] [Closed]: WIP: " Chocimier
2021-02-19 16:56 ` Chocimier
2021-02-19 21:17 ` ericonr
2021-02-19 21:19 ` [PR REVIEW] " ericonr
2021-02-19 21:45 ` [PR PATCH] [Updated] " Eluminae
2021-02-19 21:47 ` [PR REVIEW] " Eluminae
2021-02-19 21:47 ` Eluminae
2021-02-19 21:47 ` Eluminae [this message]
2021-02-19 21:48 ` Eluminae
2021-02-19 22:08 ` ericonr
2021-02-21 18:24 ` Gottox
2021-02-21 18:25 ` Gottox
2021-02-21 18:25 ` [PR PATCH] [Closed]: " Gottox
2021-02-22 20:28 ` Gottox
2021-02-23  8:03 ` [PR REVIEW] " Eluminae
2021-02-23  8:27 ` [PR PATCH] [Updated] " Eluminae
2021-02-23  8:35 ` Eluminae

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=20210219214757.qhbLCzU3iWtCoRjy7e_x_cbiBrUeeS0xTw6nDItcXqw@z \
    --to=eluminae@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).