From: Paul Eggleton <paul.eggleton@linux.intel.com>
To: bitbake-devel@lists.openembedded.org
Subject: [PATCH 0/1] Allow resuming interrupted fetch
Date: Mon, 16 Jan 2012 15:01:07 +0000 [thread overview]
Message-ID: <cover.1326725777.git.paul.eggleton@linux.intel.com> (raw)
This patch fixes an annoyance of mine that I've observed others running
into, where (either due to network issues or deliberate Ctrl+C) a fetch
is interrupted and won't properly resume the next time.
The patch (against Poky, but applies cleanly with -p2 against bitbake
master) is available in the git repository at:
git://git.yoctoproject.org/poky-contrib paule/fetchresume
http://git.yoctoproject.org/cgit.cgi/poky-contrib/log/?h=paule/fetchresume
Paul Eggleton (1):
bitbake/fetch2: allow resuming interrupted fetch
bitbake/lib/bb/fetch2/__init__.py | 6 +++---
1 files changed, 3 insertions(+), 3 deletions(-)
--
1.7.5.4
next reply other threads:[~2012-01-16 15:09 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-16 15:01 Paul Eggleton [this message]
2012-01-16 15:01 ` [PATCH 1/1] bitbake/fetch2: allow resuming interrupted fetch Paul Eggleton
2012-01-20 16:41 ` Richard Purdie
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=cover.1326725777.git.paul.eggleton@linux.intel.com \
--to=paul.eggleton@linux.intel.com \
--cc=bitbake-devel@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