From: William Hubbs <williamh@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] [PATCH v4 0/1] go modules eclass round 4
Date: Mon, 30 Sep 2019 17:22:22 -0500 [thread overview]
Message-ID: <20190930222222.GA25342@whubbs1.dev.av1.gaikai.org> (raw)
In-Reply-To: <20190930170423.16528-1-williamh@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 366 bytes --]
On Mon, Sep 30, 2019 at 12:04:22PM -0500, William Hubbs wrote:
> William Hubbs (1):
> go-module.eclass: new eclass for go modules
>
> eclass/go-module.eclass | 177 ++++++++++++++++++++++++++++++++++++++++
> 1 file changed, 177 insertions(+)
> create mode 100644 eclass/go-module.eclass
>
> --
> 2.21.0
This is committed.
Thanks,
William
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2019-09-30 22:22 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-30 17:04 [gentoo-dev] [PATCH v4 0/1] go modules eclass round 4 William Hubbs
2019-09-30 17:04 ` [gentoo-dev] [PATCH v4 1/1] go-module.eclass: new eclass for go modules William Hubbs
2019-09-30 22:22 ` William Hubbs [this message]
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=20190930222222.GA25342@whubbs1.dev.av1.gaikai.org \
--to=williamh@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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