Github messages for voidlinux
 help / color / mirror / Atom feed
From: akhiljalagam <akhiljalagam@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: New package: xremap-0.4.4
Date: Thu, 21 Jul 2022 12:49:37 +0200	[thread overview]
Message-ID: <20220721104937.g6ViwaskaeQwjq8zpCEIpkiiXNBls-HrFKeRsKcG98U@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-38149@inbox.vuxu.org>

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

New comment by akhiljalagam on void-packages repository

https://github.com/void-linux/void-packages/pull/38149#issuecomment-1191336767

Comment:
> > _I didn't know that._ Well downloading 300MB of qemu just to get completions seems like a solution. My comment is pretty useless now. This is an interesting way to solve this.
> 
> Just for reference, [here's an example](https://github.com/void-linux/void-packages/blob/c8aa5e65f18faaf1f3b3fcb7dc237cd5aa8d118f/srcpkgs/github-cli/template#L30) (GitHub CLI).

thanks. added shell completions.

  parent reply	other threads:[~2022-07-21 10:49 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-20  7:16 [PR PATCH] " akhiljalagam
2022-07-20  7:28 ` [PR REVIEW] " meator
2022-07-20  7:29 ` [PR PATCH] [Updated] " akhiljalagam
2022-07-20  7:30 ` akhiljalagam
2022-07-20 13:22 ` tranzystorek-io
2022-07-20 15:15 ` meator
2022-07-20 15:20 ` tranzystorek-io
2022-07-20 15:38 ` meator
2022-07-21  2:51 ` gbrlsnchs
2022-07-21 10:48 ` [PR PATCH] [Updated] " akhiljalagam
2022-07-21 10:48 ` akhiljalagam
2022-07-21 10:49 ` akhiljalagam [this message]
2022-07-21 10:58 ` [PR REVIEW] " tranzystorek-io
2022-07-21 11:02 ` akhiljalagam
2022-07-21 11:02 ` akhiljalagam
2022-07-21 11:03 ` tranzystorek-io
2022-07-21 11:04 ` [PR PATCH] [Updated] " akhiljalagam
2022-07-21 11:14 ` meator
2022-10-20  2:14 ` github-actions
2022-11-04  2:13 ` [PR PATCH] [Closed]: " github-actions

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=20220721104937.g6ViwaskaeQwjq8zpCEIpkiiXNBls-HrFKeRsKcG98U@z \
    --to=akhiljalagam@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).