From: Peter Staubach <staubach@redhat.com>
To: "J. Bruce Fields" <bfields@fieldses.org>
Cc: nfs@lists.sourceforge.net,
"Steinar H. Gunderson" <sesse@debian.org>,
398058@bugs.debian.org
Subject: Re: nhfsstone license
Date: Mon, 20 Nov 2006 17:24:52 -0500 [thread overview]
Message-ID: <45622B34.2080407@redhat.com> (raw)
In-Reply-To: <20061120222034.GD12285@fieldses.org>
J. Bruce Fields wrote:
> On Mon, Nov 20, 2006 at 10:53:05PM +0100, Steinar H. Gunderson wrote:
>
>> If we cannot get this resolved, we'd have to remove nhfsstone from
>> Debian main, which would be rather painful (if nothing else because
>> we'd have to modify the upstream tarball)
>>
>
> No modification required if we remove it from upstream too. Do people
> use it?
Considering that nhfsstone was the precursor to the precursor for SPECsfs,
what would people use it for? Perhaps it should be part of a testsuite
collection, but it doesn't seem particularly useful in a normal context.
Thanx...
ps
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
NFS maillist - NFS@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/nfs
next prev parent reply other threads:[~2006-11-20 22:25 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-20 21:53 nhfsstone license Steinar H. Gunderson
2006-11-20 22:20 ` J. Bruce Fields
2006-11-20 22:24 ` Peter Staubach [this message]
2006-11-20 22:26 ` Steinar H. Gunderson
2006-12-14 2:12 ` Steinar H. Gunderson
2006-12-18 22:49 ` Neil Brown
2006-12-18 22:52 ` Steinar H. Gunderson
2006-11-22 2:27 ` Marty Leisner
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=45622B34.2080407@redhat.com \
--to=staubach@redhat.com \
--cc=398058@bugs.debian.org \
--cc=bfields@fieldses.org \
--cc=nfs@lists.sourceforge.net \
--cc=sesse@debian.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.