From: Christian <evilninja@gmx.net>
To: reiserfs-list@namesys.com
Subject: Re: new reiser4progs?
Date: Fri, 18 Feb 2005 17:43:19 +0100 [thread overview]
Message-ID: <42161B27.9040408@gmx.net> (raw)
In-Reply-To: <200502181717.30090.vitaly@namesys.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Vitaly Fertman wrote:
> testing a release candidate before releasing.
> the amount of time needed depends on the amount of problems
> appeared, if debugging/fixing/bugfix testing is need, etc.
would it be an option to publish daily (nightly) builds, along with a big.
fat UNTESTED warning? it could be done via scripts and even if it does not
build one day or the other - users would notice that and could report.
thanks,
Christian.
- --
BOFH excuse #88:
Boss' kid fucked up the machine
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFCFhsmC/PVm5+NVoYRAnoJAJsFDRGMwm4B6cJcSvKse9vlO0D+KACg74Vx
bA/rsyNUcZk5SPplUFkDXYs=
=41fL
-----END PGP SIGNATURE-----
next prev parent reply other threads:[~2005-02-18 16:43 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-18 8:31 new reiser4progs? Ookhoi
2005-02-18 13:19 ` Vitaly Fertman
2005-02-18 14:08 ` Ookhoi
2005-02-18 14:17 ` Vitaly Fertman
2005-02-18 16:43 ` Christian [this message]
2005-02-19 0:49 ` David Masover
2005-02-21 18:10 ` Hans Reiser
2005-02-20 9:49 ` Vitaly Fertman
2005-02-21 13:15 ` Ookhoi
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=42161B27.9040408@gmx.net \
--to=evilninja@gmx.net \
--cc=reiserfs-list@namesys.com \
/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.