From: Larry McVoy <lm@bitmover.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Larry McVoy <lm@bitmover.com>,
LinuxPPC Dev <linuxppc-dev@lists.linuxppc.org>
Subject: Re: linuxppc_2_5 snapshots
Date: Thu, 18 Jan 2001 10:43:01 -0800 [thread overview]
Message-ID: <20010118104301.O6787@work.bitmover.com> (raw)
In-Reply-To: <20010115112211.L29026@opus.bloom.county>
On Mon, Jan 15, 2001 at 11:22:11AM -0700, Tom Rini wrote:
> Does bk2.0beta support resuming of clones?
No, but we will add this if we can't fix the socket problem. We'd really
rather fix it right, the fact that you would ever need the resume indicates
we screwed up. Or, I suppose, that your net connection dropped. Hmm. Maybe
it's worth it.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-18 18:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-15 16:33 linuxppc_2_5 snapshots Chris Boot
2001-01-15 17:32 ` Larry McVoy
2001-01-15 18:22 ` Tom Rini
2001-01-18 18:43 ` Larry McVoy [this message]
2001-01-18 18:52 ` Tom Rini
2001-01-16 16:06 ` Chris Boot
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=20010118104301.O6787@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).