From: Matan Peled <chaosite@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] why gentoo doesn't have long description?
Date: Wed, 24 Aug 2005 09:48:40 +0300 [thread overview]
Message-ID: <430C1848.7020609@gmail.com> (raw)
In-Reply-To: <558b73fb05082320393c29effc@mail.gmail.com>
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael Crute wrote:
> Or you could use http://packages.gentoo.org/ or
> http://gentoo-portage.com both of which tend to provide decent
> information about the packages in portage.
>
> -Mike
Well, first of all, top-posting sucks, especially in a thread which has already
begun as bottom-posting.
Second, the whole idea is to do this for non-connected systems. Meaning, a
solution not involving the Internet... =)
- --
[Name ] :: [Matan I. Peled ]
[Location ] :: [Israel ]
[Public Key] :: [0xD6F42CA5 ]
[Keyserver ] :: [keyserver.kjsl.com]
encrypted/signed plain text preferred
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDDBhIA7Qvptb0LKURAvaFAJ9DbYkSfHqxchHjRkkpcSM9GeL9xACfST+3
yq3iNNG0NlY/pIqaofPgvpg=
=CpoX
-----END PGP SIGNATURE-----
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2005-08-24 6:53 UTC|newest]
Thread overview: 51+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-08-23 11:26 [gentoo-user] why gentoo doesn't have long description? conan
2005-08-23 15:45 ` Jonas Geiregat
2005-08-23 21:47 ` Ciaran McCreesh
2005-08-24 3:39 ` Michael Crute
2005-08-24 6:48 ` Matan Peled [this message]
2005-08-24 7:01 ` Jonas Geiregat
2005-08-24 11:08 ` Fernando Canizo
2005-08-24 14:03 ` Michael Crute
2005-08-24 14:24 ` David Morgan
2005-08-24 14:39 ` Michael Crute
2005-08-24 14:49 ` David Morgan
2005-08-24 14:57 ` Daniel da Veiga
2005-08-24 15:08 ` [gentoo-user] very OT (was: why gentoo doesn't have long description?) Christoph Gysin
2005-08-24 15:13 ` [gentoo-user] why gentoo doesn't have long description? David Morgan
2005-08-24 15:19 ` Ciaran McCreesh
2005-08-24 17:14 ` Michael Crute
2005-08-24 17:33 ` Matan Peled
2005-08-24 18:00 ` Michael Crute
2005-08-24 20:33 ` Jonathan Nichols
2005-08-24 20:52 ` Holly Bostick
2005-08-24 22:40 ` Jonathan Nichols
2005-08-24 21:14 ` Anthony E. Caudel
2005-08-24 21:22 ` Volker Armin Hemmann
2005-08-24 21:24 ` Dave Nebinger
2005-08-24 21:25 ` Ciaran McCreesh
2005-08-24 21:45 ` Jerry McBride
2005-08-24 21:54 ` David Morgan
2005-08-24 22:43 ` Jonathan Nichols
2005-08-25 15:42 ` A. Khattri
2005-08-25 16:49 ` Michael Crute
2005-08-26 2:05 ` W.Kenworthy
2005-08-26 7:36 ` Marco Matthies
2005-08-26 14:17 ` A. Khattri
2005-08-24 23:01 ` Anthony E. Caudel
2005-08-25 0:11 ` Matt Nordhoff
2005-08-25 15:39 ` A. Khattri
2005-08-25 21:52 ` Neil Bothwick
2005-08-26 14:36 ` Billy Holmes
2005-08-26 15:06 ` Daniel da Veiga
2005-08-26 15:21 ` Holly Bostick
2005-08-26 15:40 ` Martin Marcher
2005-08-26 17:10 ` Neil Bothwick
2005-08-26 18:29 ` A. Khattri
2005-08-24 15:03 ` Jonas Geiregat
2005-08-24 15:01 ` Jonas Geiregat
2005-08-24 20:23 ` [gentoo-user] " Moshe Kaminsky
2005-08-25 23:57 ` [gentoo-user] " Holly Bostick
2005-08-26 0:19 ` Nick Rout
2005-08-26 13:12 ` Fernando Canizo
2005-08-29 20:02 ` Jonas Geiregat
2005-08-29 19:31 ` Holly Bostick
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=430C1848.7020609@gmail.com \
--to=chaosite@gmail.com \
--cc=gentoo-user@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