All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Nick Warne <nick@linicks.net>, Chris Adams <cmadams@hiwaay.net>,
	linux-kernel@vger.kernel.org
Subject: Re: Red Hat ES4 GPL Issues?
Date: Thu, 23 Feb 2006 11:15:58 -0700	[thread overview]
Message-ID: <43FDFBDE.2040304@wolfmountaingroup.com> (raw)
In-Reply-To: <1140713030.4672.75.camel@laptopd505.fenrus.org>

Arjan van de Ven wrote:

>>But anyway, what has this thread to do with the kernel?
>>    
>>
>
>
>since when does something need to be on-topic for Jeff Merkey to post to
>lkml ? ;-)
>
>  
>

I got the RPM's and located them from an earlier responder to the post.  
It was just disturbing
that RedHat does ont include the sources when you install from binary -- 
which they always have
before. 

Thought I would ask folks since this is where people raise GPL inquiries 
(at least as a first step),
and it appeared to be the right place becuase the issue was resolved 
within 5 minutes of the post.
I do kernel development in a company that supports Linux and ships Linux 
appliances and I
have a lot of significant and valuable kernel development, so kernel 
development issues,
like "Where the hell have they hidden Linus' source code" are relevant.

I am glad Red Hat is still distributing the code, but I am disappointed 
they are no longer
including it in the base RPM install.

Jeff

>-
>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:[~2006-02-23 17:19 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-02-23  0:11 Red Hat ES4 GPL Issues? Jeff V. Merkey
2006-02-22 23:21 ` Joel Jaeggli
2006-02-23  0:19   ` Jeff V. Merkey
2006-02-23  8:50 ` Arjan van de Ven
2006-02-23 14:59 ` Chris Adams
2006-02-23 16:31   ` Nick Warne
2006-02-23 16:43     ` Arjan van de Ven
2006-02-23 18:15       ` Jeff V. Merkey [this message]
2006-02-23 17:47         ` Arjan van de Ven
2006-02-23 18:45           ` Jeff V. Merkey
2006-02-23 19:38             ` Lennart Sorensen
2006-02-27  8:02               ` Ingo Molnar
2006-02-24  4:29             ` jdow

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=43FDFBDE.2040304@wolfmountaingroup.com \
    --to=jmerkey@wolfmountaingroup.com \
    --cc=arjan@infradead.org \
    --cc=cmadams@hiwaay.net \
    --cc=linux-kernel@vger.kernel.org \
    --cc=nick@linicks.net \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.