linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alan Cox <alan@lxorguk.ukuu.org.uk>
To: zippel@linux-m68k.org (Roman Zippel)
Cc: alan@lxorguk.ukuu.org.uk (Alan Cox),
	davem@redhat.com (David S. Miller),
	lm@bitmover.com, pavel@ucw.cz, linux-kernel@vger.kernel.org
Subject: Re: Bitkeeper licence issues
Date: Thu, 21 Mar 2002 20:54:05 +0000 (GMT)	[thread overview]
Message-ID: <E16o9ZV-0006EZ-00@the-village.bc.nu> (raw)
In-Reply-To: <Pine.LNX.4.21.0203201520280.20018-100000@serv> from "Roman Zippel" at Mar 21, 2002 08:14:19 PM

> themselves, they just buy it. The interesting point here is that their
> biggest threat is now a technology which is not really disruptive, but
> rather a technology they can't buy.

Read the book - buying into the new technology as an old company can 
actually have dire results when you buy in. It is studied. 

> repeating work. Most development which is moved to india is also the type
> of development which is most likely to be automated by better tools. So if
> india just relies on this it will be hit very badly.

Read the book 8)


  reply	other threads:[~2002-03-21 20:38 UTC|newest]

Thread overview: 55+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-03-18 21:26 Bitkeeper licence issues Pavel Machek
2002-03-18 22:42 ` Larry McVoy
2002-03-18 23:14   ` Pavel Machek
2002-03-18 23:22     ` Dave Jones
2002-03-18 23:43       ` Pavel Machek
2002-03-19  8:35         ` Rik van Riel
2002-03-19  2:02       ` Larry McVoy
2002-03-19  8:21         ` Gerd Knorr
2002-03-19 15:11           ` Larry McVoy
2002-03-19 21:58         ` Pavel Machek
2002-03-19 22:04           ` Larry McVoy
     [not found]         ` <20020319215800.GN12260@atrey.karlin.m__.cuni.cz>
2002-03-20 22:42           ` Ton Hospel
2002-03-19 22:06       ` Pavel Machek
2002-03-19 23:25         ` Larry McVoy
2002-03-19 23:27           ` David S. Miller
2002-03-19 23:44             ` Larry McVoy
2002-03-19 23:45               ` David S. Miller
2002-03-19 23:54                 ` Matthew Kirkwood
2002-03-19 23:56               ` Ben Collins
2002-03-20 17:23               ` Martin Dalecki
2002-03-20 17:51                 ` Alan Cox
2002-03-20 18:04                   ` Martin Dalecki
2002-03-20 20:34                     ` Neil Booth
2002-03-19 23:34           ` Tom Rini
2002-03-20  0:09             ` Alan Cox
2002-03-24 11:44             ` Thunder from the hill
2002-03-20  7:57           ` Alexander Viro
2002-03-19  0:00     ` yodaiken
2002-03-19  1:29       ` David S. Miller
2002-03-19  1:18   ` Roman Zippel
2002-03-19  1:37     ` David S. Miller
2002-03-19 18:42       ` Roman Zippel
2002-03-19 19:09         ` Alan Cox
2002-03-19 20:01           ` Shane Nay
2002-03-19 23:08           ` Rik van Riel
2002-03-19 23:19             ` Robert Love
2002-03-19 23:26               ` Rik van Riel
2002-03-19 23:42                 ` Davide Libenzi
2002-03-19 23:31             ` yodaiken
2002-03-19 23:47               ` Larry McVoy
2002-03-20  0:02                 ` Thomas Dodd
2002-03-20  0:19                 ` Theodore Tso
2002-03-20  0:57                   ` Petko Manolov
2002-03-21 19:44                 ` Mark H. Wood
2002-03-21 20:29                   ` Shane Nay
2002-03-27 14:40                 ` Henning P. Schmiedehausen
2002-03-20  0:05               ` James Simmons
2002-03-19 20:35                 ` Andreas Dilger
2002-03-20  0:14                 ` Kurt Ferreira
2002-03-20  2:16                   ` Greg Hennessy
2002-03-20  0:57             ` Richard Gooch
2002-03-21 19:14           ` Roman Zippel
2002-03-21 20:54             ` Alan Cox [this message]
2002-03-22  0:02               ` Roman Zippel
2002-03-19  1:44     ` Anton Altaparmakov

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=E16o9ZV-0006EZ-00@the-village.bc.nu \
    --to=alan@lxorguk.ukuu.org.uk \
    --cc=davem@redhat.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    --cc=pavel@ucw.cz \
    --cc=zippel@linux-m68k.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).