From: Martin Jansa <martin.jansa@gmail.com>
To: Christopher Larson <kergoth@gmail.com>
Cc: "bitbake-devel@lists.openembedded.org"
<bitbake-devel@lists.openembedded.org>
Subject: Re: [RFC PATCH 0/5] Implement git shallow mirror tarball support
Date: Tue, 18 Aug 2015 10:45:20 +0200 [thread overview]
Message-ID: <20150818084520.GF2458@jama> (raw)
In-Reply-To: <CABcZAN=qS5Hc2KMr2bazenmfoPDdU2fL_3TqAYedGWr=jnH17A@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2344 bytes --]
On Fri, Aug 14, 2015 at 08:57:17AM -0700, Christopher Larson wrote:
> On Thu, Aug 13, 2015 at 4:46 PM, Christopher Larson <kergoth@gmail.com>
> wrote:
>
> > From: Christopher Larson <chris_larson@mentor.com>
> >
> > Please review the following changes for suitability for inclusion. If you
> > have
> > any objections or suggestions for improvement, please respond to the
> > patches. If
> > you agree with the changes, please provide your Acked-by.
> >
> > This only implements support for shallow mirror tarballs, not shallow
> > clones.
> >
> > The mirror tarball filename includes branch, revision, and depth. To
> > enable,
> > use the `BB_GIT_SHALLOW` variable, or `BB_GIT_SHALLOW_<name>` for specific
> > URLs. This variable can hold either a clone depth (e.g. `1` to just get
> > SRCREV), or a ref or commit, in which case we keep history up to that
> > commit.
> >
> > The shallow support will not, at this time, function correctly for
> > linux-yocto, due to its branching scheme & validation.
> >
> > Example:
> >
> > BB_GIT_SHALLOW ?= "1"
> > BB_GIT_SHALLOW_pn-linux-yocto = ""
> > BB_GIT_SHALLOW_pn-linux-mel_mx6 = "v3.14"
> > BB_GIT_SHALLOW_pn-testrepo = "testbranch"
> >
> > This implementation will attempt to fetch a full mirror tarball if it was
> > unable to fetch a shallow tarball. If `BB_GIT_SHALLOW` and
> > `BB_GENERATE_MIRROR_TARBALLS` are enabled for a given recipe, a shallow
> > tarball will be emitted.
It would be nice to describe what this implementation does when there is
some local git clone already (will it first try to update it with "git fetch"
or download shallow tarball?)
> >
>
> I forgot to mention, this implements [YOCTO #7958](
> https://bugzilla.yoctoproject.org/show_bug.cgi?id=7958).
it also looks like more proper fix for [YOCTO #1511](
https://bugzilla.yoctoproject.org/show_bug.cgi?id=1511).
> --
> Christopher Larson
> kergoth at gmail dot com
> Founder - BitBake, OpenEmbedded, OpenZaurus
> Maintainer - Tslib
> Senior Software Engineer, Mentor Graphics
> --
> _______________________________________________
> bitbake-devel mailing list
> bitbake-devel@lists.openembedded.org
> http://lists.openembedded.org/mailman/listinfo/bitbake-devel
--
Martin 'JaMa' Jansa jabber: Martin.Jansa@gmail.com
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 188 bytes --]
next prev parent reply other threads:[~2015-08-18 8:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-08-13 23:46 [RFC PATCH 0/5] Implement git shallow mirror tarball support Christopher Larson
2015-08-13 23:46 ` [RFC PATCH 1/5] bb.fetch.git: add support for shallow mirror tarballs Christopher Larson
2015-08-13 23:46 ` [RFC PATCH 2/5] bb.fetch.git: truncate branches to SRCREV Christopher Larson
2015-08-13 23:46 ` [RFC PATCH 3/5] bb.fetch: simplify mirror tarball handling in try_mirror_url Christopher Larson
2015-08-13 23:46 ` [RFC PATCH 4/5] bb.fetch: support ud.mirrortarballs Christopher Larson
2015-08-13 23:46 ` [RFC PATCH 5/5] bb.fetch.git: use ud.mirrortarballs Christopher Larson
2015-08-14 15:53 ` [RFC PATCH 0/5] Implement git shallow mirror tarball support Christopher Larson
2015-08-14 15:57 ` Christopher Larson
2015-08-18 8:45 ` Martin Jansa [this message]
2015-08-18 14:28 ` Christopher Larson
2015-08-18 18:35 ` Christopher Larson
2015-08-18 18:51 ` Martin Jansa
2015-08-18 22:44 ` Christopher Larson
2015-08-18 23:51 ` Christopher Larson
2015-08-14 16:54 ` Christopher Larson
2015-08-26 16:38 ` Christopher Larson
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=20150818084520.GF2458@jama \
--to=martin.jansa@gmail.com \
--cc=bitbake-devel@lists.openembedded.org \
--cc=kergoth@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 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.