From: Akshat Kumar <akumar@mail.nanosouffle.net>
To: Fans of the OS Plan 9 from Bell Labs <9fans@9fans.net>
Subject: Re: [9fans] partial cp
Date: Tue, 26 Jan 2010 23:27:00 -0800 [thread overview]
Message-ID: <fe41879c1001262327l487e7933v5ed7df451c4959ed@mail.gmail.com> (raw)
In-Reply-To: <32d987d51001261751xf61ad2bx91189896d1a66b95@mail.gmail.com>
On Tue, Jan 26, 2010 at 5:51 PM, Federico G. Benavento
<benavento@gmail.com> wrote:
> hget does something similar, don't know, I'll usually
> just restart copying the file.
that's a little much in this case (big file, going over the local network)
> On Tue, Jan 26, 2010 at 6:03 PM, maht <maht-9fans@maht0x0r.net> wrote:
>> If you're going to start hacking fcp then just add a switch that says
>> 'resume' and it works out the offset for you
I'd be happy to add that. Hopefully others will find it useful also.
Thanks,
ak
prev parent reply other threads:[~2010-01-27 7:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-25 1:45 Akshat Kumar
2010-01-25 17:15 ` maht
2010-01-26 19:55 ` roger peppe
2010-01-26 20:03 ` maht
2010-01-27 1:51 ` Federico G. Benavento
2010-01-27 7:27 ` Akshat Kumar [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=fe41879c1001262327l487e7933v5ed7df451c4959ed@mail.gmail.com \
--to=akumar@mail.nanosouffle.net \
--cc=9fans@9fans.net \
/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;
as well as URLs for NNTP newsgroup(s).