From: ericonr <ericonr@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [do not merge] texlive: make tlmgr work and split libsynctex
Date: Sun, 16 Aug 2020 07:30:37 +0200 [thread overview]
Message-ID: <20200816053037.BTrXLCncZORRU4YrJE4gSCWR3UVQdDFa6znABG-IdVo@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24300@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 391 bytes --]
New comment by ericonr on void-packages repository
https://github.com/void-linux/void-packages/pull/24300#issuecomment-674481548
Comment:
I need to clean up my work tree, the number of files there makes me miss symlinks all the time D:
Anything else I should solve?
Also, commit https://github.com/void-linux/void-packages/pull/24305/commits/a810b574f1007f1d3724bb5992577df01398f5e3
next prev parent reply other threads:[~2020-08-16 5:30 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-15 23:41 [PR PATCH] texlive: make tlmgr work fosslinux
2020-08-15 23:42 ` [PR PATCH] [Updated] " fosslinux
2020-08-16 1:13 ` [PR REVIEW] " ericonr
2020-08-16 1:26 ` fosslinux
2020-08-16 1:38 ` fosslinux
2020-08-16 2:28 ` ericonr
2020-08-16 2:52 ` fosslinux
2020-08-16 2:53 ` [PR PATCH] [Updated] " fosslinux
2020-08-16 2:54 ` [PR REVIEW] " ericonr
2020-08-16 2:55 ` ericonr
2020-08-16 4:07 ` ericonr
2020-08-16 4:10 ` fosslinux
2020-08-16 4:12 ` ericonr
2020-08-16 4:12 ` ericonr
2020-08-16 4:13 ` ericonr
2020-08-16 4:14 ` fosslinux
2020-08-16 4:31 ` ericonr
2020-08-16 4:36 ` [PR PATCH] [Updated] " fosslinux
2020-08-16 5:25 ` [do not merge] texlive: make tlmgr work and split libsynctex fosslinux
2020-08-16 5:29 ` ericonr
2020-08-16 5:30 ` ericonr [this message]
2020-08-16 5:36 ` fosslinux
2020-08-16 8:04 ` fosslinux
2020-08-16 8:07 ` [PR PATCH] [Updated] " fosslinux
2020-08-17 13:48 ` [PR PATCH] [Closed]: " 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=20200816053037.BTrXLCncZORRU4YrJE4gSCWR3UVQdDFa6znABG-IdVo@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).