From: Alin Nastac <mrness@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] why went unusable versions stable?
Date: Sun, 13 Mar 2005 02:51:01 +0200 [thread overview]
Message-ID: <42338E75.1030602@gentoo.org> (raw)
In-Reply-To: <1110590519.10977.1.camel@localhost>
[-- Attachment #1: Type: text/plain, Size: 980 bytes --]
Olivier Crête wrote:
>uOn Sat, 2005-12-03 at 01:01 +0100, Ernst Herzberg wrote:
>
>
>>dev-util/esvn:
>>
>>0.6.8-r1 was masked, and has some crazy bugs, that this stuff is not usable
>>for an 'enduser'. If you select an 'working directory', the last character of
>>the path get lost. You have to create a workspace, select there a working
>>directory, add the last character by hand....
>>
>>OkOk, as long as this stuff is masked, no problem. BUT: Upstream has released
>>a new version with this bug fixed. Why went the buggy version stable? And the
>>new with the bug fixed version is masked? That make no sense to me.
>>
>>Can somebody explain that?
>>
>>
>
>Maybe you should ask MrNess... But he doesn't seem to think that testing
>is important...
>
>
>
This package I happen to use at work, I could say I did more than a
simple test.
Do you suggest that, if this bug is real, I should know about?
Do you understand that tests don't always detect bugs, right?
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 256 bytes --]
next prev parent reply other threads:[~2005-03-13 0:51 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 0:01 [gentoo-dev] why went unusable versions stable? Ernst Herzberg
2005-03-12 1:19 ` Mike Frysinger
2005-03-12 3:12 ` Ernst Herzberg
2005-03-12 4:08 ` Brian Jackson
2005-03-12 4:20 ` Stephen P. Becker
2005-03-12 1:21 ` Olivier Crête
2005-03-13 0:51 ` Alin Nastac [this message]
2005-03-13 9:48 ` Olivier Crête
2005-03-13 9:57 ` Alin Nastac
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=42338E75.1030602@gentoo.org \
--to=mrness@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox