From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Gary Thomas <gary@mlbassoc.com>,
openembedded-core@lists.openembedded.org
Subject: Re: [PATCH 0/2] Fixes for len(TMPDIR) == 410
Date: Wed, 06 Apr 2016 11:13:29 +0100 [thread overview]
Message-ID: <1459937609.7348.201.camel@linuxfoundation.org> (raw)
In-Reply-To: <5704D900.3000505@mlbassoc.com>
On Wed, 2016-04-06 at 11:38 +0200, Gary Thomas wrote:
> On 2016-04-06 11:30, Robert Yang wrote:
> > The following changes since commit
> > b2dc5a68e74dafedf7960ef77ad3d73912ed7960:
> >
> > bdwgc: use github repo for source location (2016-04-05 11:48:09
> > +0100)
> >
> > are available in the git repository at:
> >
> > git://git.openembedded.org/openembedded-core-contrib rbt/long
> > http://cgit.openembedded.org/cgit.cgi/openembedded-core-contrib/
> > log/?h=rbt/long
> >
> > Robert Yang (2):
> > sanity.bbclass: fix a hardcode in check_path_length()
> > wget: fix build when len(TMPDIR) == 410
> >
> > meta/classes/sanity.bbclass | 2 +-
> > meta/recipes-extended/wget/wget.inc | 5 +++++
> > 2 files changed, 6 insertions(+), 1 deletion(-)
> >
>
> How are these patches related and what is magic about a path length
> of 410?
> Are you sure that it might not be 569 on my system for example?
410 is the maximum we've ever managed to make work for the core
recipes. We're basically trying to ensure we don't get worse. In an
ideal world there wouldn't be any restrictions but that would take
significant resource investment for questionable return.
Cheers,
Richard
prev parent reply other threads:[~2016-04-06 10:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-06 9:30 [PATCH 0/2] Fixes for len(TMPDIR) == 410 Robert Yang
2016-04-06 9:30 ` [PATCH 1/2] sanity.bbclass: fix a hardcode in check_path_length() Robert Yang
2016-04-06 9:30 ` [PATCH 2/2] wget: fix build when len(TMPDIR) == 410 Robert Yang
2016-04-06 9:38 ` [PATCH 0/2] Fixes for " Gary Thomas
2016-04-06 10:13 ` Richard Purdie [this message]
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=1459937609.7348.201.camel@linuxfoundation.org \
--to=richard.purdie@linuxfoundation.org \
--cc=gary@mlbassoc.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