From: "Kris Warkentin" <kewarken@qnx.com>
To: <gdb@sources.redhat.com>, "Ken Dyck" <Ken.Dyck@dspfactory.com>
Subject: Re: [RFC] upload/download command
Date: Mon, 17 Nov 2003 18:01:00 -0000 [thread overview]
Message-ID: <046b01c3ad35$020accc0$0202040a@catdog> (raw)
In-Reply-To: <OF1D1B484E.12ED2F63-ON05256DE1.0057AE18@dspfactory.com>
I would say the most common meaning for upload is to push something onto a
remote target and download means to pull something off a remote. Ie. "I
just downloaded 10 GB of pr0n from that server." or "I just uploaded the
virus to the mainframe."
This is the sense in which we use the terms.
cheers,
Kris
----- Original Message -----
From: "Ken Dyck" <Ken.Dyck@dspfactory.com>
To: <kewarken@qnx.com>; <gdb@sources.redhat.com>
Sent: Monday, November 17, 2003 11:22 AM
Subject: RE: [RFC] upload/download command
>Our QNX pdebug protocol supports an upload/download command.
>This is handy
>for putting binaries onto target system and getting back things like
>corefiles.
Out of curiosity, which way is up? In some circles, particularly in DSP
development, which I am most familiar with (I'm not sure if it extends
to the rest of the embedded community), the term 'download' usually
refers to pushing data down onto the target from the host machine. In
the internet world, on the other hand, the term is used to mean pulling
some data down from a remote machine onto a local host. In what sense is
the pdebug protocol using the terms?
Ken
next prev parent reply other threads:[~2003-11-17 18:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-17 16:22 Ken Dyck
2003-11-17 18:01 ` Kris Warkentin [this message]
2003-11-18 3:08 ` Andrew Cagney
2003-11-18 15:03 ` Kris Warkentin
-- strict thread matches above, loose matches on Subject: below --
2003-11-17 15:18 Kris Warkentin
2003-11-17 15:26 ` Daniel Jacobowitz
2003-11-17 15:34 ` Kris Warkentin
2003-11-17 15:39 ` Daniel Jacobowitz
2003-11-17 15:51 ` Andrew Cagney
2003-11-17 15:42 ` Andrew Cagney
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='046b01c3ad35$020accc0$0202040a@catdog' \
--to=kewarken@qnx.com \
--cc=Ken.Dyck@dspfactory.com \
--cc=gdb@sources.redhat.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