From: Rusty Russell <rusty@rustcorp.com.au>
To: Jeff Garzik <jgarzik@pobox.com>
Cc: Andrew Morton <akpm@osdl.org>,
lkml - Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [TRIVIAL] doc update for bk usage
Date: Thu, 20 May 2004 18:36:09 +1000 [thread overview]
Message-ID: <1085042169.7541.29.camel@bach> (raw)
In-Reply-To: <40AC65E5.40403@pobox.com>
On Thu, 2004-05-20 at 18:01, Jeff Garzik wrote:
> Rusty Russell wrote:
> > From: carbonated beverage <ramune@net-ronin.org>
> >
> > ---
> > bk://... appears to be dead, use http://... instead.
...
> NAK.
>
> It's not dead, as I just re-verified (and usually do so daily).
Great; that's why I cc'd lkml. I don't use bk.
I'll close it.
Rusty.
--
Anyone who quotes me in their signature is an idiot -- Rusty Russell
prev parent reply other threads:[~2004-05-20 8:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-20 7:08 [TRIVIAL] doc update for bk usage Rusty Russell
2004-05-20 8:01 ` Jeff Garzik
2004-05-20 8:36 ` Rusty Russell [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=1085042169.7541.29.camel@bach \
--to=rusty@rustcorp.com.au \
--cc=akpm@osdl.org \
--cc=jgarzik@pobox.com \
--cc=linux-kernel@vger.kernel.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