From: "Maciej Barć" <xgqt@gentoo.org>
To: gentoo-dev@lists.gentoo.org, Florian Schmaus <flow@gentoo.org>
Subject: Re: [gentoo-dev] RFC: new gradle.eclass
Date: Fri, 6 Jan 2023 18:51:54 +0100 [thread overview]
Message-ID: <f59081ba-3a0f-6834-a12f-659495e0eae3@gentoo.org> (raw)
In-Reply-To: <20230106172051.274199-1-flow@gentoo.org>
[-- Attachment #1.1.1: Type: text/plain, Size: 448 bytes --]
Hallelujah! Finally support for Gradle!
Thank you so much for taking time to implement it!
On 1/6/23 18:20, Florian Schmaus wrote:
> Happy new year everyone!
>
> I'd like to as for a review of an initial eclass for gradle. This is my
> first eclass, so I am sure there is plenty to find. ;)
>
> The related github PR is https://github.com/gentoo/gentoo/pull/28986
>
> - Flow
>
>
--
Have a great day!
~ Maciej XGQT Barć
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 10875 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 495 bytes --]
next prev parent reply other threads:[~2023-01-06 17:52 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-06 17:20 [gentoo-dev] RFC: new gradle.eclass Florian Schmaus
2023-01-06 17:20 ` [gentoo-dev] [PATCH] gradle.eclass: add new eclass Florian Schmaus
2023-01-07 4:29 ` Sam James
2023-01-07 10:58 ` Florian Schmaus
2023-01-07 6:07 ` Anna
2023-01-06 17:51 ` Maciej Barć [this message]
2023-01-06 18:52 ` [gentoo-dev] RFC: new gradle.eclass Yuan Liao (Leo)
2023-01-06 19:40 ` Florian Schmaus
2023-06-28 7:52 ` [gentoo-dev] [PATCH 0/2] " Florian Schmaus
2023-06-28 7:52 ` [gentoo-dev] [PATCH 1/2] gradle.eclass: add new eclass Florian Schmaus
2023-06-28 8:51 ` Michał Górny
2023-06-28 9:21 ` Ulrich Mueller
2023-06-28 7:52 ` [gentoo-dev] [PATCH 2/2] dev-java/openjfx: switch to gradle.eclass Florian Schmaus
2023-06-30 8:39 ` [gentoo-dev] [PATCH 0/2] new gradle.eclass Sam James
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=f59081ba-3a0f-6834-a12f-659495e0eae3@gentoo.org \
--to=xgqt@gentoo.org \
--cc=flow@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