From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] How well supported is collision-protect?
Date: Wed, 27 Apr 2005 20:37:10 -0400 [thread overview]
Message-ID: <200504272037.10393.vapier@gentoo.org> (raw)
In-Reply-To: <20050428002920.GA9023@lion.gg3.net>
On Wednesday 27 April 2005 08:29 pm, Georgi Georgiev wrote:
> - How well is it expected to work?
it's expected to work just fine
> - Do you guys expect bug reports about packages with conflicting
> targets, with possible patches, etc?
yes
-mike
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2005-04-28 0:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-28 0:29 [gentoo-dev] How well supported is collision-protect? Georgi Georgiev
2005-04-28 0:37 ` Mike Frysinger [this message]
2005-04-28 1:14 ` Georgi Georgiev
2005-04-28 1:27 ` Mike Frysinger
2005-04-28 2:40 ` Chris Gianelloni
2005-04-28 4:52 ` Rumen Yotov
2005-04-28 4:59 ` Mike Frysinger
2005-04-28 22:51 ` [gentoo-dev] " R Hill
2005-04-28 1:41 ` [gentoo-dev] " Marius Mauch
2005-04-28 2:19 ` Alec Warner
2005-04-28 0:50 ` Hasan Khalil
2005-04-28 12:10 ` Michael Cummings
2005-04-28 12:49 ` Georgi Georgiev
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=200504272037.10393.vapier@gentoo.org \
--to=vapier@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