From: NeelChotai <NeelChotai@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: github-cli: update to 0.12.0.
Date: Thu, 17 Sep 2020 20:05:33 +0200 [thread overview]
Message-ID: <20200917180533.xsWy0gFn28hYoIR2h0vbBg29a_78ezIUUobMLwPtsmA@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-24775@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 169 bytes --]
New comment by NeelChotai on void-packages repository
https://github.com/void-linux/void-packages/pull/24775#issuecomment-694405720
Comment:
1.0.0 got released today.
next prev parent reply other threads:[~2020-09-17 18:05 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-09 6:01 [PR PATCH] " shizonic
2020-09-17 18:05 ` NeelChotai
2020-09-17 18:05 ` NeelChotai [this message]
2020-09-17 23:08 ` [PR REVIEW] " mcbloch
2020-09-17 23:08 ` mcbloch
2020-09-18 7:47 ` [PR PATCH] [Updated] " shizonic
2020-09-18 7:51 ` github-cli: update to 1.0.0 shizonic
2020-09-19 22:01 ` [PR PATCH] [Merged]: " Johnnynator
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=20200917180533.xsWy0gFn28hYoIR2h0vbBg29a_78ezIUUobMLwPtsmA@z \
--to=neelchotai@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).