linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andre Hedrick <andre@linux-ide.org>
To: Mike Fedyk <mfedyk@matchmail.com>
Cc: Ihar Philips Filipau <filia@softhome.net>, linux-kernel@vger.kernel.org
Subject: Re: OT: Vanilla not for embedded?! Re: Kernel 2.6 size increase - get_current()?
Date: Fri, 25 Jul 2003 13:43:16 -0700 (PDT)	[thread overview]
Message-ID: <Pine.LNX.4.10.10307251342141.24466-100000@master.linux-ide.org> (raw)
In-Reply-To: <20030725204613.GB1686@matchmail.com>


Where is the "deep" fork storaged, sounds interesting!
At lets it should buisness friendly.

-a

On Fri, 25 Jul 2003, Mike Fedyk wrote:

> On Fri, Jul 25, 2003 at 05:37:39PM +0200, Ihar Philips Filipau wrote:
> > P.S. Offtopic. As I see it Linux & Linus have made the decision of 
> > optimization. Linux after all is capitalismus creation: who has more 
> > money do control everything. Server market has more money - they do more
> > work on kernel and they systems are not that far from developers' 
> > workstations - so Linux gets more and more server/workstation oriented. 
> > This will fit desktop market too - if your computer was made to run 
> > WinXP AKA exp(bloat) - it will be capable to run any OS. Linus repeating 
> > 'small is beatiful' sounds more and more like crude joke...
> > As for embedded market - it is already in deep fork and far far away 
> > from vanilla kernels... Vanilla really not that relevant to real world...
> 
> Vanilla will be what people put into it.  And I have seen more messages from
> embedded people complaining, than actually doing and submitting patches for
> merging.
> 
> So the embedded trees are a deep fork huh?  Did you or anyone else do
> anything to merge during 2.5?!
> 
> And now you see why there is a "deep" fork...
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/
> 


  reply	other threads:[~2003-07-25 20:36 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <d2nx.4QV.15@gated-at.bofh.it>
     [not found] ` <dbTZ.5Z5.19@gated-at.bofh.it>
2003-07-25 15:37   ` [uClinux-dev] Kernel 2.6 size increase - get_current()? Ihar "Philips" Filipau
2003-07-25 20:46     ` OT: Vanilla not for embedded?! " Mike Fedyk
2003-07-25 20:43       ` Andre Hedrick [this message]
2003-07-27 11:57       ` Ihar "Philips" Filipau
2003-07-27 13:05         ` Francois Romieu
     [not found] <dcQ9.7aj.35@gated-at.bofh.it>
     [not found] ` <dcQ9.7aj.31@gated-at.bofh.it>
     [not found]   ` <dhFS.3R3.11@gated-at.bofh.it>
     [not found]     ` <dSm7.4TZ.5@gated-at.bofh.it>
     [not found]       ` <dTrN.5Te.7@gated-at.bofh.it>
2003-07-27 14:33         ` Ihar "Philips" Filipau
     [not found] <dUQT.72E.5@gated-at.bofh.it>
     [not found] ` <dUQT.72E.7@gated-at.bofh.it>
     [not found]   ` <dUQT.72E.9@gated-at.bofh.it>
     [not found]     ` <dUQT.72E.11@gated-at.bofh.it>
     [not found]       ` <dUQT.72E.13@gated-at.bofh.it>
     [not found]         ` <dUQT.72E.3@gated-at.bofh.it>
2003-07-27 14:47           ` Ihar "Philips" Filipau

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=Pine.LNX.4.10.10307251342141.24466-100000@master.linux-ide.org \
    --to=andre@linux-ide.org \
    --cc=filia@softhome.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mfedyk@matchmail.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;
as well as URLs for NNTP newsgroup(s).