From: Phil Blundell <philb@gnu.org>
To: Patches and discussions about the oe-core layer
<openembedded-core@lists.openembedded.org>
Subject: Re: [PATCH 01/12] gcc: Switch SRC_URI to use svn
Date: Fri, 10 Aug 2012 10:30:42 +0100 [thread overview]
Message-ID: <1344591043.23275.286.camel@phil-desktop> (raw)
In-Reply-To: <660D912D-3A89-418B-B091-145567C25656@dominion.thruhere.net>
On Fri, 2012-08-10 at 11:22 +0200, Koen Kooi wrote:
> Op 10 aug. 2012, om 11:07 heeft Phil Blundell <philb@gnu.org> het volgende geschreven:
>
> > On Fri, 2012-08-10 at 09:47 +0100, Paul Eggleton wrote:
> >> On Friday 10 August 2012 10:03:06 Koen Kooi wrote:
> >>> Op 9 aug. 2012, om 03:25 heeft Khem Raj <raj.khem@gmail.com> het volgende
> >> geschreven:
> >>>> svn tar balls are 96M as compared to 1.3G git tars
> >>>> its unnessary to suck in that much of data.
> >>>
> >>> That's indeed a big difference and also expected, with svn you only get
> >>> revision N and N-1, with git you get everything. But even so, I can fetch
> >>> that 1.3GB a *lot* faster than that 0.1GB svn. Maybe I'm on the wrong side
> >>> of the ocean, but that gcc svn server is sloooooooooooooooooooooow.
> >>
> >> FWIW the git option was much, much, much slower for us here in the UK.
> >
> > Maybe we should just go back to using the released tarballs for gcc
> > rather than any sort of SCM checkout. That would be an 80MB download
> > for the tar.bz2 and of course you can get it from your local mirror.
> >
> > I think the original reason we switched to using the SCM checkout was
> > that, at the time, we were carrying around a huge number of backported
> > patches that hadn't quite made it into any released version yet.
>
> We pointed it at the release branch, so updating from x.y.0 to x.y.4 was just a srcrev change. But the same can be done by exporting the patches with git-format-patch and importing them into the OE tree.
Right. Or, once x.y.4 actually gets released, it would be available as
a tarball in its own right anyway. The only time when it's at all
tricky is the period just before that happens, when there are
potentially-important fixes in the gcc-x.y branch that aren't yet in any
released version. But, as you say, we can just import those as patches
and I think/hope their number should be fairly limited.
p.
next prev parent reply other threads:[~2012-08-10 9:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-09 1:25 [PATCH 01/12] gcc: Switch SRC_URI to use svn Khem Raj
2012-08-09 1:25 ` [PATCH 02/12] eglibc-2.16: Update to top of 2.16 branch Khem Raj
2012-08-10 8:03 ` [PATCH 01/12] gcc: Switch SRC_URI to use svn Koen Kooi
2012-08-10 8:47 ` Paul Eggleton
2012-08-10 9:07 ` Phil Blundell
2012-08-10 9:22 ` Koen Kooi
2012-08-10 9:30 ` Phil Blundell [this message]
2012-08-10 14:55 ` Khem Raj
2012-08-10 9:19 ` Koen Kooi
2012-08-10 12:38 ` Colin Walters
2012-08-10 12:42 ` Martin Jansa
2012-08-10 10:31 ` Enrico Scholz
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=1344591043.23275.286.camel@phil-desktop \
--to=philb@gnu.org \
--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 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.