From: sgn <sgn@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [DO NOT MERGE] tmux: update to 3.1. And claim maintainer
Date: Sun, 26 Apr 2020 03:13:26 +0200 [thread overview]
Message-ID: <20200426011326.GoGHaPLQB0ATii5AIQ_flT5iuchzJsWz3ySPYSC0ffE@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-21331@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 204 bytes --]
New comment by sgn on void-packages repository
https://github.com/void-linux/void-packages/pull/21331#issuecomment-619463177
Comment:
I see a recent CPU spike. Let me check if it's because of new tmux.
next prev parent reply other threads:[~2020-04-26 1:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-25 15:25 [PR PATCH] " sgn
2020-04-26 1:13 ` sgn [this message]
2020-04-26 23:48 ` sgn
2020-04-27 14:27 ` [not yet] " sgn
2020-04-29 13:36 ` sgn
2020-04-29 13:57 ` q66
2020-04-29 13:57 ` [PR PATCH] [Merged]: " 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=20200426011326.GoGHaPLQB0ATii5AIQ_flT5iuchzJsWz3ySPYSC0ffE@z \
--to=sgn@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).