From: "Gregory Anders" <greg@gpanders.com>
To: Jack Mitchell <ml@embed.me.uk>
Cc: zboszor@pr.hu, Khem Raj <raj.khem@gmail.com>,
openembedded-devel@lists.openembedded.org
Subject: Re: [oe] Upstream scipy recipe to meta-openembedded
Date: Thu, 15 Jul 2021 13:08:15 +0000 [thread overview]
Message-ID: <YPAzP4jMI/KIJeEd@gpanders.com> (raw)
In-Reply-To: <f0c2e1bc-0e24-1b7a-f9ff-ca85c9cd9856@embed.me.uk>
On Thu, 15 Jul 2021 09:44 +0100, Jack Mitchell wrote:
>Hi Greg,
>
>I should be able to take it over as I'll continue to be using it in the
>future. How do you want to transfer ownership, shall I fork it and you
>point to the new repo on the master branch, or can you get github to
>re-direct to the new home?
Thanks Jack. I believe I can simply transfer the repo to your user on
GitHub. You should receive an email asking for your confirmation.
prev parent reply other threads:[~2021-07-15 13:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-07-12 15:19 Upstream scipy recipe to meta-openembedded Gregory Anders
2021-07-12 16:01 ` [oe] " Khem Raj
2021-07-13 10:20 ` Zoltan Boszormenyi
2021-07-13 10:46 ` Jack Mitchell
2021-07-13 13:09 ` Gregory Anders
2021-07-15 8:44 ` Jack Mitchell
2021-07-15 13:08 ` Gregory Anders [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=YPAzP4jMI/KIJeEd@gpanders.com \
--to=greg@gpanders.com \
--cc=ml@embed.me.uk \
--cc=openembedded-devel@lists.openembedded.org \
--cc=raj.khem@gmail.com \
--cc=zboszor@pr.hu \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.