From: Edward Shishkin <edward.shishkin@gmail.com>
To: Jeff Mahoney <jeffm@suse.com>
Cc: Alex Caudill <alex@erudified.com>, reiserfs-devel@vger.kernel.org
Subject: Re: A few questions
Date: Mon, 24 Mar 2008 03:18:17 +0300 [thread overview]
Message-ID: <47E6F349.6010208@gmail.com> (raw)
In-Reply-To: <47CDAD5A.505@suse.com>
Jeff Mahoney wrote:
> Alex Caudill wrote:
>
> >Hi,
>
> >With namesys.com being down, I can't find reiser4 documentation, and,
> >frankly, that sucks.
>
> >I'm prepared to:
>
> >1.) Provide free hosting for ReiserFS version control and documentation.
>
> >2.) Provide an erudified.com subdomain or purchase a top-level domain
> >for the same.
>
> >3.) Make a reasonable donation via PayPal to anyone willing to
> >transfer Reiser4 documentation and code onto a new machine. I'm also
> >willing to help with this.
>
>
> I agree something needs to be done here, and appreciate the offer, but
> I'm afraid it's one that we can't accept. I'm sure your hosting is
> perfectly adequate, but hosting for tools that millions of people use
> (or at least have on their systems) requires a high level of trust. The
> trust just isn't there. I'm sure you're perfectly trustworthy, but we
> don't know you. I've been hoping to get space on kernel.org
Eventually we have got it.
Btw, it seems you are lucky.. :)
> or, failing
> that, sourceforge. These sites are accepted nearly universally as
> trustworthy, and have gobs of bandwidth as well as extensive mirroring
> and backup facilities.
>
> I have space on opensuse.org that I could offer up, but I don't think
> that's the right solution since the hosting site should be distribution
> agnostic. Unfortunately, with namesys.com now, I fear that opensuse.org
> may have become the de facto location to obtain reiserfsprogs (v3)
> sources.
>
> -Jeff
>
> --
> Jeff Mahoney
> SUSE Labs
--
To unsubscribe from this list: send the line "unsubscribe reiserfs-devel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
next prev parent reply other threads:[~2008-03-24 0:18 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-04 1:04 A few questions Alex Caudill
[not found] ` <81E34349-D837-40A3-94F5-E314AAC43396@telegraphics.com.au>
2008-03-04 7:53 ` Alex Caudill
[not found] ` <b8d16a880803040025s2bac98eaq7eb24713d3c46196@mail.gmail.com>
2008-03-04 8:28 ` Fwd: " Christopher Sawtell
2008-03-04 8:57 ` Alex Caudill
2008-03-04 14:22 ` Toby Thain
2008-03-04 20:13 ` Jeff Mahoney
2008-03-04 22:06 ` Alex Caudill
2008-03-24 0:18 ` Edward Shishkin [this message]
-- strict thread matches above, loose matches on Subject: below --
2012-03-07 15:15 Yao
2012-03-07 15:52 ` Eric Paris
2012-03-07 15:57 ` David Quigley
2012-03-07 16:23 ` Stephen Smalley
2008-03-04 17:34 Mat
2005-02-02 0:19 Ian Pratt
2005-02-02 0:04 Hugo Silva
2005-02-02 0:19 ` Mark Williamson
2004-01-31 10:06 Stefan Berndtsson
2004-01-31 10:46 ` Benjamin Herrenschmidt
2004-01-31 15:44 ` Stefan Berndtsson
2004-02-02 8:36 ` Stefan Berndtsson
2002-12-01 11:02 Adam Luchjenbroers
2002-12-01 13:06 ` dashielljt
2002-12-02 6:56 ` Adam Luchjenbroers
2002-12-02 14:26 ` dashielljt
2002-12-02 14:53 ` Adam Luchjenbroers
2002-12-02 15:31 ` Jim Reimer
2002-11-15 8:20 Rocco Stanzione
2002-11-15 19:21 ` Nix N. Nix
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=47E6F349.6010208@gmail.com \
--to=edward.shishkin@gmail.com \
--cc=alex@erudified.com \
--cc=jeffm@suse.com \
--cc=reiserfs-devel@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.