From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: polybar: update to 3.5.3.
Date: Thu, 24 Dec 2020 05:45:52 +0100 [thread overview]
Message-ID: <20201224044552.j8vV6ug8RLES8-av48UkRyr8qVhH0mdSq6KBtbHN5zM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-27380@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 1735 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/27380#issuecomment-750738601
Comment:
Is
```
/usr/share/doc/polybar/.buildinfo
/usr/share/doc/polybar/_sources/dev/packaging.rst.txt
/usr/share/doc/polybar/_sources/dev/release-workflow.rst.txt
/usr/share/doc/polybar/_sources/index.rst.txt
/usr/share/doc/polybar/_sources/man/polybar.1.rst.txt
/usr/share/doc/polybar/_sources/man/polybar.5.rst.txt
/usr/share/doc/polybar/_sources/user/actions.rst.txt
/usr/share/doc/polybar/_static/alabaster.css
/usr/share/doc/polybar/_static/basic.css
/usr/share/doc/polybar/_static/custom.css
/usr/share/doc/polybar/_static/doctools.js
/usr/share/doc/polybar/_static/documentation_options.js
/usr/share/doc/polybar/_static/file.png
/usr/share/doc/polybar/_static/jquery-3.5.1.js
/usr/share/doc/polybar/_static/jquery.js
/usr/share/doc/polybar/_static/language_data.js
/usr/share/doc/polybar/_static/minus.png
/usr/share/doc/polybar/_static/plus.png
/usr/share/doc/polybar/_static/pygments.css
/usr/share/doc/polybar/_static/searchtools.js
/usr/share/doc/polybar/_static/underscore-1.3.1.js
/usr/share/doc/polybar/_static/underscore.js
/usr/share/doc/polybar/config
/usr/share/doc/polybar/dev/packaging.html
/usr/share/doc/polybar/dev/release-workflow.html
/usr/share/doc/polybar/genindex.html
/usr/share/doc/polybar/index.html
/usr/share/doc/polybar/man/polybar.1.html
/usr/share/doc/polybar/man/polybar.5.html
/usr/share/doc/polybar/objects.inv
/usr/share/doc/polybar/search.html
/usr/share/doc/polybar/searchindex.js
/usr/share/doc/polybar/user/actions.html
```
too much? I'm not sure we need to ship that part. The man pages are a good addition, though.
next prev parent reply other threads:[~2020-12-24 4:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 17:28 [PR PATCH] " pbui
2020-12-23 19:33 ` ericonr
2020-12-23 19:34 ` ericonr
2020-12-23 20:23 ` [PR PATCH] [Updated] " pbui
2020-12-23 20:24 ` pbui
2020-12-23 20:36 ` [PR PATCH] [Updated] " pbui
2020-12-24 4:45 ` ericonr [this message]
2020-12-24 15:14 ` pbui
2020-12-24 15:14 ` pbui
2020-12-24 20:26 ` [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=20201224044552.j8vV6ug8RLES8-av48UkRyr8qVhH0mdSq6KBtbHN5zM@z \
--to=ericonr@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).