From: Sarah J <sarah.j@devthusiastcraft.com>
To: git@vger.kernel.org
Subject: Re: Noômen: Gifted Invite Enclosed (Github Community Partnership)
Date: Mon, 11 May 2026 15:38:13 +0000 [thread overview]
Message-ID: <019e17ab-b10a-76b6-94c9-c5f0241eb112@devthusiastcraft.com> (raw)
In-Reply-To: <019e0d05-2060-7b52-8a61-cce41dbc2e52@devthusiastcraft.com>
Noômen, just checking if you saw my previous email.
Your GitHub profile was selected for a free lifetime membership to Devthusiast (normally $1,800/year).
If you want to join the newsletter, just reply “yes.”
Otherwise we’ll pass the spot to another engineer in 7 days.
All the best,
Team @ Devthusiast
On Sat, May 9, 2026 1:55 PM, Sarah J <sarah.j@devthusiastcraft.com>
[sarah.j@devthusiastcraft.com]> wrote:
> Hey Noômen
>
> Annually, we pick engineers from Github, and your GitHub profile https://github.com/bnhassin was selected this year.
>
> You're officially invited to a lifetime membership to devthusiast, our email newsletter for tech founders that love to tinker. And because we selected your profile, it's completely free for you.
>
> Some of what you can expect to find in our daily newsletter:
>
> - Latest in AI: Latest AI news from our inside sources at OpenAI, Anthropic and Google
> - VC Radar: The latest tech funding news, before they come out on Tech Crunch
> - AI Wars, Model Power Rankings: Today’s leaderboard of the top AI models
> - Tinker of the Week: One useful open-source tool that is flying under the radar
>
> Please respond with “yes” to acknowledge receipt of this message, or we will have to choose a different profile. Once confirmed you will get your first newsletter edition!
>
> Welcome,
> Team @ Devthusiast
>
prev parent reply other threads:[~2026-05-11 15:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-05-09 13:55 Noômen: Gifted Invite Enclosed (Github Community Partnership) Sarah J
2026-05-11 15:38 ` Sarah J [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=019e17ab-b10a-76b6-94c9-c5f0241eb112@devthusiastcraft.com \
--to=sarah.j@devthusiastcraft.com \
--cc=git@vger.kernel.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