Github messages for voidlinux
 help / color / mirror / Atom feed
From: q66 <q66@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Prefer flags over config file, again
Date: Mon, 14 Sep 2020 23:52:31 +0200	[thread overview]
Message-ID: <20200914215231.bOpqDrrO4iIIBM8XmaQzpv_a9T_MuXVdMZdBzmBu5YU@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24790@inbox.vuxu.org>

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

New comment by q66 on void-packages repository

https://github.com/void-linux/void-packages/pull/24790#issuecomment-692333712

Comment:
also, i quite fail to see what this PR is supposed to achieve, it doesn't revert the previous change, it just sources the config file in yet another place

  parent reply	other threads:[~2020-09-14 21:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-09 21:21 [PR PATCH] " Chocimier
2020-09-09 21:42 ` q66
2020-09-11 18:25 ` Chocimier
2020-09-14 21:49 ` q66
2020-09-14 21:52 ` q66
2020-09-14 21:52 ` q66 [this message]
2020-09-14 21:53 ` q66
2020-09-14 21:55 ` [PR PATCH] [Merged]: " q66
2020-09-14 21:55 ` q66

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=20200914215231.bOpqDrrO4iIIBM8XmaQzpv_a9T_MuXVdMZdBzmBu5YU@z \
    --to=q66@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).