From: "Jeff V. Merkey" <jmerkey@wolfmountaingroup.com>
To: Arjan van de Ven <arjan@infradead.org>
Cc: Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [ANNOUNCE] Wolf Mountain File System Archives and Releases
Date: Thu, 01 Dec 2005 09:39:34 -0700 [thread overview]
Message-ID: <438F2746.8030904@wolfmountaingroup.com> (raw)
In-Reply-To: <1133429704.2853.20.camel@laptopd505.fenrus.org>
Arjan van de Ven wrote:
>On Wed, 2005-11-30 at 17:10 -0700, Jeff V. Merkey wrote:
>
>
>>The Wolf Mountain File System and NWFS File System project archives for
>>Linux are now online at www.wolfmountaingroup.org. All future updates
>>and patches to Linux which are related to these projects are now
>>available at this site.
>>
>>
>
>the website is empty though; no code anywhere
>
>it's also odd that you chose CDDL for everything, I'd expect at least
>the kernel parts to be GPL (given that CDDL is not compatible with GPL)
>
>
>
>
>
I had promised Hazelton and some other folks to notify them wen I setup
the archives. Since I cannot post the code
at kernel.org ay longer, I had to setup an alternate server for NWFS
updates and WMFS. There's code there, go look again.
I am posting a bunch of patches later this week (when I get over this
flu I've had). I won't be putting out any more GPL code due to the
kernel.org
situation -- CDDL only. I also won't be giving stuff away totally for
free anymore either. I am obligated to return GPL
changes in the kernel. That's what folks are going to get, along with
some technical dialouge from time to time.
Jeff
next prev parent reply other threads:[~2005-12-01 17:06 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-01 0:10 [ANNOUNCE] Wolf Mountain File System Archives and Releases Jeff V. Merkey
2005-12-01 9:24 ` Wichert Akkerman
2005-12-01 9:35 ` Arjan van de Ven
2005-12-01 16:39 ` Jeff V. Merkey [this message]
2005-12-09 14:34 ` Jan Engelhardt
2005-12-09 16:18 ` Jeff V. Merkey
2005-12-09 18:04 ` Zwane Mwaikambo
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=438F2746.8030904@wolfmountaingroup.com \
--to=jmerkey@wolfmountaingroup.com \
--cc=arjan@infradead.org \
--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 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.