From: Alexey Brodkin <Alexey.Brodkin@synopsys.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH v2] qt5webkit: Get sources from Qt-5-unofficial-builds
Date: Wed, 16 Nov 2016 08:14:29 +0000 [thread overview]
Message-ID: <1479284015.2530.6.camel@synopsys.com> (raw)
In-Reply-To: <4b0fddb6-8bfe-42f2-b710-1bee3d9ff847@andin.de>
Hi?Andreas,
On Wed, 2016-11-16 at 08:53 +0100, Andreas Naumann wrote:
> Am 15.11.2016 um 22:20 schrieb Arnout Vandecappelle:
> >
> >
> >
> > On 15-11-16 15:07, Julien CORJON wrote:
> > >
> > > Alexey,
> > >
> > > I like the idea of fetching obsolete submodules from Qt hosting instead
> > > of external github. But, as url say it's snapshot, we will probably have
> > > to change hash file more often... Maybe we will have to get rid of hash
> > > files for theses obsolete submodules.
> >
> > ?Since the tarballs are actual versioned tarballs, I do hope that they don't
> > just change randomly...
>
> So my experience was that the tarballs in?
> 5.8.0-beta/latest_src/submodules did actually change until it was?
> properly released. That was the reason i removed the hashes in my bump?
> series (after having refreshed them initially).
> I guess the .../<number>/submodule snapshots are probably more constant?
> during the development phase, but I have no objection to leave the patch?
> as is.
Not really sure. In "numbered" folders I only see pre-built stuff like:
.exe and .dmg
So from what I may see the only source of sources is
5.8/5.8.0-beta/latest_src/.
-Alexey
next prev parent reply other threads:[~2016-11-16 8:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-11-09 13:59 [Buildroot] [PATCH v2] qt5webkit: Get sources from Qt-5-unofficial-builds Alexey Brodkin
2016-11-15 14:07 ` Julien CORJON
2016-11-15 21:20 ` Arnout Vandecappelle
2016-11-16 7:53 ` Andreas Naumann
2016-11-16 8:14 ` Alexey Brodkin [this message]
2016-11-16 8:21 ` Andreas Naumann
2016-11-15 22:41 ` Thomas Petazzoni
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=1479284015.2530.6.camel@synopsys.com \
--to=alexey.brodkin@synopsys.com \
--cc=buildroot@busybox.net \
/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.