mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Stelian Pop <stelian@popies.net>
To: lm@bitmover.com, andersen@codepoet.org,
	Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: BKCVS broken ?
Date: Fri, 18 Mar 2005 15:21:25 +0100	[thread overview]
Message-ID: <20050318142124.GA3333@crusoe.alcove-fr> (raw)
In-Reply-To: <20050318141345.GA2227@bitmover.com>

On Fri, Mar 18, 2005 at 06:13:45AM -0800, Larry McVoy wrote:

> On Fri, Mar 18, 2005 at 10:00:49AM +0100, Stelian Pop wrote:
> > On Thu, Mar 17, 2005 at 10:38:53PM -0800, Larry McVoy wrote:
> > 
> > > Hey, it's open source, I'm hoping that people will take that code and
> > > evolve it do whatever they need.  We're willing to do what we can on
> > > this end if people need protocol changes to support new features, 
> > > time permitting.  Think of that code as a prototype.  It's really
> > > simple, you can hack it trivially.
> > 
> > 	------------
> > 	if (strncmp("bk://", p, 5)) return (1);
> > 	------------
> > 
> > Any chance this could be made to work over http ?
> 
> I don't see why not.  It will take some hacking though.  Can you live 
> without it for a bit or is it urgent?

It's not urgent at all...

Thanks.

Stelian.
-- 
Stelian Pop <stelian@popies.net>

  reply	other threads:[~2005-03-18 14:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17 14:45 Stelian Pop
2005-03-17 15:43 ` Catalin Marinas
2005-03-17 15:44 ` Larry McVoy
2005-03-18  3:07   ` H. Peter Anvin
2005-03-18  0:10 ` Larry McVoy
2005-03-18  5:50   ` Erik Andersen
2005-03-18  6:38     ` Larry McVoy
2005-03-18  9:00       ` Stelian Pop
2005-03-18 14:13         ` Larry McVoy
2005-03-18 14:21           ` Stelian Pop [this message]
2005-03-18 15:08             ` Hong Kong Phoey
2005-03-18 22:09               ` Stelian Pop
2005-03-19 14:52 ` Larry McVoy

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=20050318142124.GA3333@crusoe.alcove-fr \
    --to=stelian@popies.net \
    --cc=andersen@codepoet.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.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

all inboxes | Powered by JetHome®