From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Alexander Kanavin <alex.kanavin@gmail.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 7/8] mesa: switch over to official git
Date: Fri, 31 May 2019 17:25:11 +0100 [thread overview]
Message-ID: <b22d487548905237681a0d8ea2c18a17da1714c2.camel@linuxfoundation.org> (raw)
In-Reply-To: <20190531155612.75663-7-alex.kanavin@gmail.com>
On Fri, 2019-05-31 at 17:56 +0200, Alexander Kanavin wrote:
> The tarballs for all versions prior to 18.x have been moved to
> https://mesa.freedesktop.org/archive/older-versions/
>
> To avoid this practice causing fetching failures in the future,
> let's use the git.
I'm really not sure we want to move things over to git, it does end up
making the build process slower as they take longer to fetch, unpack
and clean up :/.
Cheers,
Richard
next prev parent reply other threads:[~2019-05-31 16:25 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-31 15:56 [PATCH 1/8] liburcu: update to 0.11.0 Alexander Kanavin
2019-05-31 15:56 ` [PATCH 2/8] perl: update to 5.30.0 Alexander Kanavin
2019-05-31 15:56 ` [PATCH 3/8] python3-pygments: add a recipe Alexander Kanavin
2019-05-31 15:56 ` [PATCH 4/8] gtk-doc: upgrade 1.29 -> 1.30 Alexander Kanavin
2019-06-01 6:31 ` Richard Purdie
2019-06-01 11:27 ` Alexander Kanavin
2019-05-31 15:56 ` [PATCH 5/8] source-highlight: remove the recipe Alexander Kanavin
2019-05-31 15:56 ` [PATCH 6/8] piglit: upgrade to latest revision Alexander Kanavin
2019-05-31 15:56 ` [PATCH 7/8] mesa: switch over to official git Alexander Kanavin
2019-05-31 16:25 ` Richard Purdie [this message]
2019-05-31 16:27 ` Burton, Ross
2019-06-01 11:31 ` Alexander Kanavin
2019-05-31 15:56 ` [PATCH 8/8] mesa-demos: switch to using " Alexander Kanavin
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=b22d487548905237681a0d8ea2c18a17da1714c2.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=alex.kanavin@gmail.com \
--cc=openembedded-core@lists.openembedded.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