From: Jason Wever <weeve@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] dhcpcd-1.3.22_p4-r10 testing request
Date: Fri, 3 Jun 2005 08:44:10 -0600 (MDT) [thread overview]
Message-ID: <Pine.LNX.4.63.0506030843160.28695@stargazer.weeve.org> (raw)
In-Reply-To: <1117789644.11358.3.camel@uberlaptop.ubernet>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Fri, 3 Jun 2005, Roy Marples wrote:
> I've just put net-misc/dhcpcd-1.3.22_p4-r10 into portage, package.masked
> If some kind people would like to test it for me so I don't break our
> happy go lucky ~ARCH users I would be grateful :)
Best way to ensure you get the testing and verification you want on this
is to file a bug, assign it to yourself or your herd, and CC the relevant
arches.
Thanks,
- --
Jason Wever
Gentoo/Sparc Co-Team Lead
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFCoGy8dKvgdVioq28RAvpRAJ98piVKckktENdu2SQ10c3yos7/ZACfQDrd
CiiRI2iDMA3ngrEFbLFZiic=
=Qc7u
-----END PGP SIGNATURE-----
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-06-03 14:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-06-03 9:07 [gentoo-dev] dhcpcd-1.3.22_p4-r10 testing request Roy Marples
2005-06-03 14:44 ` Jason Wever [this message]
2005-06-03 15:18 ` Roy Marples
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=Pine.LNX.4.63.0506030843160.28695@stargazer.weeve.org \
--to=weeve@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