From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: Jason Wessel <jason.wessel@windriver.com>
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 0/4] fetch2: fixes and optimizations
Date: Thu, 14 Jun 2012 14:05:56 +0100 [thread overview]
Message-ID: <1339679156.24333.78.camel@ted> (raw)
In-Reply-To: <1339643381-23026-1-git-send-email-jason.wessel@windriver.com>
On Wed, 2012-06-13 at 22:09 -0500, Jason Wessel wrote:
> * The fetcher logging is broken in a way where it doesnt return errors.
I merged this.
> * There is a regression in the URI handling
I've merged an alternative patch for this that was being discussed which
fixes another part of the problem.
> * Local git mirrors do not work correctly as PRE-MIRRORS
This isn't the correct fix for this problem IMO, this needs needs a bit
more work. I'll try and take a look at this problem.
> * The fall back fetch can be optimized to use clone -s
> if it is a local file url with a PRE-MIRROR
I've replied to this.
Cheers,
Richard
prev parent reply other threads:[~2012-06-14 13:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-14 3:09 [PATCH 0/4] fetch2: fixes and optimizations Jason Wessel
2012-06-14 3:09 ` [PATCH 1/4] fetch2: Fix missing output from stderr in fetcher logs Jason Wessel
2012-06-14 3:09 ` [PATCH 2/4] fetch2: Fix URI encode / decode regression Jason Wessel
2012-06-14 3:09 ` [PATCH 3/4] fetch2: Allow local git trees as pre-mirrors Jason Wessel
2012-06-14 3:09 ` [PATCH 4/4] fetch2/git.py: Optimize clone fall back when it is local Jason Wessel
2012-06-14 13:03 ` Richard Purdie
2012-06-14 13:33 ` Jason Wessel
2012-06-14 14:26 ` Richard Purdie
2012-06-14 14:31 ` Jason Wessel
2012-06-14 21:11 ` Jason Wessel
2012-06-14 13:05 ` 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=1339679156.24333.78.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=jason.wessel@windriver.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