From: "Steinar H. Gunderson" <sgunderson@bigfoot.com>
To: Neil Brown <neilb@suse.de>
Cc: "J. Bruce Fields" <bfields@fieldses.org>,
nfs@lists.sourceforge.net, 398058@bugs.debian.org
Subject: Re: nhfsstone license
Date: Mon, 18 Dec 2006 23:52:02 +0100 [thread overview]
Message-ID: <20061218225202.GA18493@uio.no> (raw)
In-Reply-To: <17799.6912.961640.948936@cse.unsw.edu.au>
On Tue, Dec 19, 2006 at 09:49:36AM +1100, Neil Brown wrote:
>> It seems like nobody does, judging from the response. Is there any chance of
>> a relatively quick 1.0.11 without nhfsstone? We have frozen in Debian at the
>> moment, but fixing such a license bug would probably be allowed past the
>> freeze.
> I've removed nhfstone from the git repository, but I'm not going to
> roll up an 1.0.11 release just now - sorry.
> Maybe in January.
No hard feelings, we're just going to fix it for the next release instead, I
guess. :-)
/* Steinar */
--
Homepage: http://www.sesse.net/
-------------------------------------------------------------------------
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-12-18 22:52 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
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 [this message]
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=20061218225202.GA18493@uio.no \
--to=sgunderson@bigfoot.com \
--cc=398058@bugs.debian.org \
--cc=bfields@fieldses.org \
--cc=neilb@suse.de \
--cc=nfs@lists.sourceforge.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox