From: prateekmedia <prateekmedia@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: Update Flameshot to v11.0.0
Date: Sun, 23 Jan 2022 13:24:17 +0100 [thread overview]
Message-ID: <20220123122417.-RCfXbmIb9LIQy3vZe_qqbRa2m-Ogow-07kfOPb3QzM@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35194@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 449 bytes --]
New comment by prateekmedia on void-packages repository
https://github.com/void-linux/void-packages/pull/35194#issuecomment-1019474172
Comment:
> > Done! I was not cloning the repo cause it was more than 400Mb in size, but anyways.
>
> If you didn't clone this repository, how did you test this package? We generally require build and runtime testing.
I was using git clone --depth 1 before so it was 12 MB in size + vpsm to build package.
next prev parent reply other threads:[~2022-01-23 12:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-35194@inbox.vuxu.org>
2022-01-23 11:20 ` oreo639
2022-01-23 11:21 ` oreo639
2022-01-23 11:27 ` oreo639
2022-01-23 12:13 ` [PR PATCH] [Updated] " prateekmedia
2022-01-23 12:14 ` prateekmedia
2022-01-23 12:21 ` paper42
2022-01-23 12:23 ` prateekmedia
2022-01-23 12:24 ` prateekmedia [this message]
2022-01-23 12:25 ` paper42
2022-01-23 12:26 ` [PR PATCH] [Updated] " prateekmedia
2022-01-23 18:37 ` flameshot: update to 11.0.0 prateekmedia
2022-01-23 18:42 ` oreo639
2022-01-23 21:41 ` [PR PATCH] [Merged]: " paper42
2022-01-23 10:38 [PR PATCH] Update Flameshot to v11.0.0 prateekmedia
2022-01-23 10:42 ` oreo639
2022-01-23 11:13 ` prateekmedia
2022-01-23 11:15 ` oreo639
2022-01-23 11:16 ` oreo639
2022-01-23 11:17 ` oreo639
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=20220123122417.-RCfXbmIb9LIQy3vZe_qqbRa2m-Ogow-07kfOPb3QzM@z \
--to=prateekmedia@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).