From: Johnnynator <Johnnynator@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: [PR REVIEW] ghidra: update to 10.1.1.
Date: Wed, 29 Dec 2021 14:43:38 +0100 [thread overview]
Message-ID: <20211229134338.n-31T6tNzkmdUN6031BZ8JYIQZTqPscScYmY4RUYeJw@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-34749@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 275 bytes --]
New review comment by Johnnynator on void-packages repository
https://github.com/void-linux/void-packages/pull/34749#discussion_r776332577
Comment:
Do not use `master` but either a tag or a commit.
Using a branch will sooner or later break the build due to changed files.
next prev parent reply other threads:[~2021-12-29 13:43 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-29 4:09 [PR PATCH] " unspecd
2021-12-29 13:43 ` Johnnynator [this message]
2021-12-30 0:31 ` [PR PATCH] [Updated] " unspecd
2021-12-30 0:53 ` [PR REVIEW] " unspecd
2021-12-30 1:13 ` [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=20211229134338.n-31T6tNzkmdUN6031BZ8JYIQZTqPscScYmY4RUYeJw@z \
--to=johnnynator@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).