From: Stefan Schweizer <genstef@gentoo.org>
To: gentoo-dev@gentoo.org
Subject: [gentoo-dev] Re: nxserver-freenx-0.5.0 to be masked
Date: Sat, 29 Apr 2006 00:41:45 +0200 [thread overview]
Message-ID: <e2u5n4$3nt$1@sea.gmane.org> (raw)
In-Reply-To: 1146258369.2967.14.camel@demandred.gnqs.org
Stuart Herbert wrote:
> nxserver-freenx-0.5.0 is in the ~arch tree by mistake. It will be
> masked just as soon as my DSL connection stays up long enough for me to
> cvs up.
What is the reason for the mask? Modular Xorg incompatibility in nx-x11?
I guess "testing" does not really count after two months in ~x86
By the way masking something afterwards is bad habit because it will cause
downgrades. Downgrades can be harmful because they can cause bugs to come
up again that have been fixed in the latest version.
- Stefan
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2006-04-28 22:54 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-04-28 21:06 [gentoo-dev] nxserver-freenx-0.5.0 to be masked Stuart Herbert
2006-04-28 22:41 ` Stefan Schweizer [this message]
2006-04-29 20:09 ` [gentoo-dev] " Stuart Herbert
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='e2u5n4$3nt$1@sea.gmane.org' \
--to=genstef@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@lists.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