public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Vojtech Pavlik <vojtech@suse.cz>
To: Martin Dalecki <dalecki@evision-ventures.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [bk+patch] Let (WIP) be replaced with (EXPERIMENTAL)
Date: Sun, 28 Apr 2002 21:24:29 +0200	[thread overview]
Message-ID: <20020428212429.A12005@ucw.cz> (raw)
In-Reply-To: <20020428142415.A10747@ucw.cz> <3CCBFAB6.7060607@evision-ventures.com>

On Sun, Apr 28, 2002 at 03:35:50PM +0200, Martin Dalecki wrote:

> Uz.ytkownik Vojtech Pavlik napisa?:
> > ChangeSet@1.571, 2002-04-28 14:22:33+02:00, vojtech@twilight.ucw.cz
> >   This removes the CONFIG_IDEDMA_PCI_WIP option, replacing it with
> >   the more common CONFIG_EXPERIMENTAL. It also adds a depencency
> >   on $CONFIG_EXPERIMENTAL where missing.
> 
> 
> All fine and all will be taken. However please note that
> I don't use BK and I don't intend too. My rejection of
> it isn't based on any idiotic policy - I found it just ugly to
> use and I was confused about the beta-alpha versions
> offered on the web site - too much work in progress for my taste.
> Finally I don't entrust source code to programmers who even don't know
> the difference between TCP and UDP and use TCP becouse they don't know better.

Ok - your decision. If you want, I'll omit the BK part of the patches.
On the other hand, if you could just forward it to Linus as is (or let
me send it to Linus after your confirmation), change comments won't get
lost. 

> I preferr a classical diff -urN ;-).

It's included, anyway.

-- 
Vojtech Pavlik
SuSE Labs

  reply	other threads:[~2002-04-28 19:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-28 12:24 [bk+patch] Let (WIP) be replaced with (EXPERIMENTAL) Vojtech Pavlik
2002-04-28 13:35 ` Martin Dalecki
2002-04-28 19:24   ` Vojtech Pavlik [this message]
2002-04-28 18:49     ` Martin Dalecki
2002-04-28 22:44       ` Vojtech Pavlik
2002-04-28 14:02 ` Martin Dalecki

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=20020428212429.A12005@ucw.cz \
    --to=vojtech@suse.cz \
    --cc=dalecki@evision-ventures.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