Github messages for voidlinux
 help / color / mirror / Atom feed
From: travankor <travankor@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [WIP] New package: void-docs-2020.04.18.
Date: Fri, 01 May 2020 03:46:54 +0200	[thread overview]
Message-ID: <20200501014654.3p6MTv9c2ZfrhkcGRAu0X81lfbNEUbGuCqd511KuJy8@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21453@inbox.vuxu.org>

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

New comment by travankor on void-packages repository

https://github.com/void-linux/void-packages/pull/21453#issuecomment-622209050

Comment:
Can the live cd's just use master of void-docs, like they do with void-packages (i.e. use the lastest version of everything when generated)? I don't know what @bobertlo says, but release tagging might be too bureaucratic.

  parent reply	other threads:[~2020-05-01  1:46 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21453@inbox.vuxu.org>
2020-04-29 18:11 ` Chocimier
2020-04-29 22:09 ` ericonr
2020-04-30 11:31 ` travankor
2020-04-30 11:31 ` travankor
2020-04-30 11:43 ` travankor
2020-04-30 14:35 ` ericonr
2020-05-01  1:46 ` travankor [this message]
2020-05-01  1:47 ` travankor
2020-05-01 17:25 ` Chocimier
2020-05-01 23:10 ` CameronNemo
2020-05-02 21:26 ` bobertlo
2020-05-02 21:33 ` bobertlo
2020-05-02 23:50 ` [PR PATCH] [Updated] " ericonr
2020-05-03  0:04 ` ericonr
2020-05-17  4:33 ` [PR PATCH] [Updated] " ericonr
2020-06-01  5:16 ` ericonr
2020-06-01  5:40 ` ericonr
2020-07-15 18:33 ` ericonr
2020-08-04  3:44 ` ericonr
2020-08-04  3:58 ` ericonr
2020-08-04  4:07 ` ericonr
2020-08-18 14:54 ` ericonr
2020-08-18 15:13 ` [PR PATCH] [Closed]: New package: void-docs-2020.08.18 ahesford

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=20200501014654.3p6MTv9c2ZfrhkcGRAu0X81lfbNEUbGuCqd511KuJy8@z \
    --to=travankor@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).