From: Mike Frysinger <vapier@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Virtual for tftp server
Date: Sun, 1 May 2011 17:42:03 -0400 [thread overview]
Message-ID: <BANLkTinuaUneZzH__JwoCET0qW=Ht2+nGg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTik8JCojYeay5h4dALciOWPyn1O_5w@mail.gmail.com>
On Sun, May 1, 2011 at 17:01, Maxim Koltsov wrote:
> 2011/5/2 Ciaran McCreesh:
>> Since suggested dependencies don't exist yet, what's wrong with just
>> elogging a message suggesting the user install a tftp server of their
>> choice?
>
> I think this is uncomfortable for user.
i dont think so. i cant see RDEPENDing on a random tftp server being
terribly useful here, and it certainly isnt a requirement. elog it
and be done.
-mike
next prev parent reply other threads:[~2011-05-01 21:46 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-01 19:04 [gentoo-dev] Virtual for tftp server Maxim Koltsov
2011-05-01 19:12 ` Aaron W. Swenson
2011-05-01 20:34 ` Maxim Koltsov
2011-05-01 20:42 ` Mike Gilbert
2011-05-01 20:41 ` Ciaran McCreesh
2011-05-01 21:01 ` Maxim Koltsov
2011-05-01 21:42 ` Mike Frysinger [this message]
2011-05-02 6:47 ` Maxim Koltsov
2011-05-02 7:52 ` Ulrich Mueller
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='BANLkTinuaUneZzH__JwoCET0qW=Ht2+nGg@mail.gmail.com' \
--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