From: "Rebecca Cran" <rebecca@bsdio.com>
To: rfc@edk2.groups.io, michael.d.kinney@intel.com,
"devel@edk2.groups.io" <devel@edk2.groups.io>,
'Bret Barkelew' <Bret.Barkelew@microsoft.com>,
Laszlo Ersek <lersek@redhat.com>,
"Gao, Liming" <liming.gao@intel.com>
Subject: Re: [edk2-rfc] [RFC] UnitTestFrameworkPkg cmocka submodule alternatives
Date: Sat, 19 Dec 2020 18:06:20 -0700 [thread overview]
Message-ID: <bd85772d-bf72-7c74-7b3a-4deb4aadbd82@bsdio.com> (raw)
In-Reply-To: <BL0PR11MB32369F11D4CE1EA929DBF69CD2C20@BL0PR11MB3236.namprd11.prod.outlook.com>
On 12/19/20 11:58 AM, Michael D Kinney wrote:
> There have been a few suggestions to create a mirror of cmocka in TianoCore
> org in GitHub.
>
> I have found a GitHub action that can do a repo sync.
>
> https://github.com/marketplace/actions/github-repo-sync
>
> I have created a temporary mirror of cmocka in my personal GitHub area that
> uses this GitHub action to sync all branches and all tags once a day.
>
> https://github.com/mdkinney/mirror-cmocka
>
> Here is the GitHub workflow file. It must be in the default branch for the
> repo using a branch name that is not present in the repo being mirrored.
> In this case, I used a branch name of 'repo-sync'.
>
> https://github.com/mdkinney/mirror-cmocka/blob/repo-sync/.github/workflows/repo-sync.yml
>
> Please provide feedback on this approach. If we like this approach, then
> I suggest we create a new repo in TianoCore called edk2-cmocka that is a
> mirror that is synced once a day and we update the cmocka submodule in the
> edk2 repo to use edk2-cmocka.
>
I'd suggest just using the Gitlab mirror. Unlike cryptomilk.org, Gitlab
should be just as reliable as Github and won't introduce another
potential failure point.
--
Rebecca Cran
next prev parent reply other threads:[~2020-12-20 1:06 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-16 18:45 [RFC] UnitTestFrameworkPkg cmocka submodule alternatives Michael D Kinney
2020-12-17 0:58 ` 回复: [edk2-devel] " gaoliming
2020-12-17 14:48 ` [edk2-rfc] " Laszlo Ersek
2020-12-17 15:54 ` Laszlo Ersek
2020-12-17 16:01 ` Rebecca Cran
2020-12-17 18:44 ` [EXTERNAL] " Bret Barkelew
2020-12-19 18:58 ` Michael D Kinney
2020-12-19 19:07 ` Bret Barkelew
2020-12-20 1:06 ` Rebecca Cran [this message]
2020-12-21 1:18 ` 回复: [edk2-devel] [edk2-rfc] " gaoliming
2020-12-21 20:14 ` Michael D Kinney
2020-12-21 20:42 ` Rebecca Cran
[not found] ` <1652D609A7BB8C97.24251@groups.io>
2020-12-21 20:44 ` Rebecca Cran
2020-12-22 0:41 ` 回复: " gaoliming
2021-02-15 0:43 ` [edk2-devel] " Rebecca Cran
2021-04-06 20:22 ` Michael D Kinney
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-list 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=bd85772d-bf72-7c74-7b3a-4deb4aadbd82@bsdio.com \
--to=devel@edk2.groups.io \
/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