From: Alexander Kanavin <alexander.kanavin@linux.intel.com>
To: Paulo Neves <ptsneves@gmail.com>
Cc: openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 14/14] babeltrace: switch over to git
Date: Fri, 4 May 2018 15:48:16 +0300 [thread overview]
Message-ID: <ff98c2cd-77b7-ff1d-7417-9868c760dd10@linux.intel.com> (raw)
In-Reply-To: <CAJO0J4hyjRyj+Zzz2Y7BTg0aB-dfEQXX4pJSi11n4Vc2iYkrJw@mail.gmail.com>
On 05/04/2018 03:46 PM, Paulo Neves wrote:
> I always wondered, what is the rationale for not always using the git
> repositories? If there is one why did we change for this specific
> recipe?
>
> I ask this because I am in the process of creating a massive layer,
> whose only purpose is to have the software come from the git
> repository and not from the tarballs of the original poky recipes.
Git repositories can be much slower to clone, than it would be to
download an equivalent tarball. Otherwise, I have no particular preference.
Alex
next prev parent reply other threads:[~2018-05-04 12:54 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-04 12:32 [PATCH 01/14] gobject-introspection: update to 1.56.1 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 02/14] ffmpeg: update to 4.0 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 03/14] vala: update to 0.40.4 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 04/14] libfm: update to 1.3.0.2 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 05/14] pcmanfm: update to 1.3.0 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 06/14] epiphany: update to 3.28.1.1 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 07/14] ca-certificates: update to 20180409 Alexander Kanavin
2018-05-08 7:47 ` Richard Purdie
2018-05-08 11:30 ` Alexander Kanavin
2018-05-04 12:32 ` [PATCH 08/14] gnome-desktop3: update to 3.28.1 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 09/14] libwebp: update to 1.0.0 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 10/14] procps: update to 3.3.14 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 11/14] webkitgtk: update to 2.20.1 Alexander Kanavin
2018-05-04 12:32 ` [PATCH 12/14] meson: update to 0.46.0 Alexander Kanavin
2018-05-04 12:43 ` Nirbheek Chauhan
2018-06-19 5:03 ` [PATCH 12/14] meson: update to 0.46.0 -- broke systemd on qemuppc Randy MacLeod
2018-06-19 5:17 ` Nirbheek Chauhan
2018-06-19 9:59 ` Burton, Ross
2018-06-19 12:01 ` Alexander Kanavin
2018-06-19 16:00 ` Khem Raj
2018-06-19 19:49 ` Burton, Ross
2018-06-19 20:06 ` Randy MacLeod
2018-06-19 20:22 ` Burton, Ross
2018-06-19 20:01 ` Randy MacLeod
2018-06-19 20:09 ` Alexander Kanavin
2018-06-19 20:24 ` Nirbheek Chauhan
2018-06-19 23:02 ` Burton, Ross
2018-06-19 23:13 ` Burton, Ross
2018-06-19 23:39 ` Khem Raj
2018-05-04 12:32 ` [PATCH 13/14] ifupdown: correct the repository location Alexander Kanavin
2018-05-04 12:32 ` [PATCH 14/14] babeltrace: switch over to git Alexander Kanavin
2018-05-04 12:46 ` Paulo Neves
2018-05-04 12:48 ` Alexander Kanavin [this message]
2018-05-04 12:55 ` Burton, Ross
2018-05-04 13:12 ` Paulo Neves
2018-05-04 13:30 ` Scott Rifenbark
2018-05-04 19:51 ` Martin Jansa
2018-05-07 10:17 ` Alexander Kanavin
2018-05-08 9:25 ` Burton, Ross
2018-05-08 15:18 ` Michael Halstead
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=ff98c2cd-77b7-ff1d-7417-9868c760dd10@linux.intel.com \
--to=alexander.kanavin@linux.intel.com \
--cc=openembedded-core@lists.openembedded.org \
--cc=ptsneves@gmail.com \
/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