From: Richard Purdie <richard.purdie@linuxfoundation.org>
To: nitin.a.kamble@intel.com
Cc: bitbake-devel@lists.openembedded.org
Subject: Re: [PATCH 1/1] bitbake wget fetcher: add parameter: downloadfilename
Date: Tue, 24 Jul 2012 10:37:16 +0100 [thread overview]
Message-ID: <1343122636.22222.1.camel@ted> (raw)
In-Reply-To: <6af334f77b2e8bdbcc536fe777c57e4ac646f71b.1342635547.git.nitin.a.kamble@intel.com>
On Wed, 2012-07-18 at 17:39 -0700, nitin.a.kamble@intel.com wrote:
> From: Nitin A Kamble <nitin.a.kamble@intel.com>
>
> this allows wget fetcher to store the downloaded file in a specified custom filename in ${DL_DIR}
>
> Exmaple:
> SRC_URI = "https://edc.intel.com/Download.aspx?id=6190;downloadfilename=LIN_IEMGD_1_14_GOLD_2443.tgz"
>
> This fixes bug:
> [YOCTO #2570]
>
> Signed-off-by: Nitin A Kamble <nitin.a.kamble@intel.com>
> ---
> bitbake/lib/bb/fetch2/wget.py | 9 ++++++++-
> 1 files changed, 8 insertions(+), 1 deletions(-)
Merged to master, thanks.
Richard
next prev parent reply other threads:[~2012-07-24 9:48 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-07-18 18:21 [PATCH 0/1] V2 add downloadfilename to wget fetcher nitin.a.kamble
2012-07-19 0:39 ` [PATCH 0/1] V2 add downloadfilename param " nitin.a.kamble
2012-07-18 18:21 ` [PATCH 1/1] bitbake wget fetcher: add parameter: downloadfilename nitin.a.kamble
2012-07-19 0:39 ` nitin.a.kamble
2012-07-24 9:37 ` Richard Purdie [this message]
2012-07-19 19:00 ` [PATCH 0/1] V2 add downloadfilename to wget fetcher Saul Wold
-- strict thread matches above, loose matches on Subject: below --
2012-07-18 18:14 [PATCH 0/1] add downloadfilename parameter to bitbake " nitin.a.kamble
2012-07-18 18:14 ` [PATCH 1/1] bitbake wget fetcher: add parameter: downloadfilename nitin.a.kamble
2012-07-18 18:14 ` nitin.a.kamble
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=1343122636.22222.1.camel@ted \
--to=richard.purdie@linuxfoundation.org \
--cc=bitbake-devel@lists.openembedded.org \
--cc=nitin.a.kamble@intel.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 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.