From: Alexander Skwar <listen@alexander.skwar.name>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Now Know Why Portage Is So Slow
Date: Sat, 27 May 2006 08:16:02 +0200 [thread overview]
Message-ID: <4477EEA2.4060108@mid.email-server.info> (raw)
In-Reply-To: <200605270025.53855.volker.armin.hemmann@tu-clausthal.de>
Hemmann, Volker Armin wrote:
> On Friday 26 May 2006 21:28, Alexander Skwar wrote:
>> Hemmann, Volker Armin wrote:
>> > On Friday 26 May 2006 18:13, Bo Ørsted Andresen wrote:
>> >> Friday 26 May 2006 17:51 skrev Hemmann, Volker Armin:
>> >> > ok, but still less to type ;)
>> >>
>> >> But esearch is more than twice as long as eix... ;)
>> >
>> > I am using search less, than syncing, so still a win, and it is only
>> > esea<tab> ;)
>>
>> Which is still 5 characters compared to 3 characters for eix :)
>>
> but eix-sync is still longer than esync (8 to 5) ;)
Nah, it's 5 to 5, so eix-sync is NOT longer than esync...
eix-<tab>
So, at best, eix is as bad as esearch, but normally eix is
faster to use - in every aspect.
Alexander Skwar
--
"May your future be limited only by your dreams."
-- Christa McAuliffe
--
gentoo-user@gentoo.org mailing list
next prev parent reply other threads:[~2006-05-27 6:23 UTC|newest]
Thread overview: 55+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-05-25 18:45 [gentoo-user] Now Know Why Portage Is So Slow Lord Sauron
2006-05-25 19:30 ` [gentoo-user] " Thomas Kirchner
2006-05-25 23:00 ` Lord Sauron
2006-05-25 23:12 ` Bo Ørsted Andresen
2006-05-26 2:12 ` Lord Sauron
2006-05-26 2:22 ` Hemmann, Volker Armin
2006-05-26 4:04 ` Ryan Tandy
2006-05-26 5:48 ` Alexander Skwar
2006-05-26 7:25 ` Neil Bothwick
2006-05-27 11:42 ` Iain Buchanan
2006-05-27 13:09 ` Alexander Skwar
2006-05-27 13:44 ` Bo Ørsted Andresen
2006-05-27 18:29 ` Lord Sauron
2006-05-28 15:06 ` [gentoo-user] " Thomas Kirchner
2006-05-29 20:52 ` Lord Sauron
2006-05-26 15:51 ` [gentoo-user] " Hemmann, Volker Armin
2006-05-26 16:13 ` Bo Ørsted Andresen
2006-05-26 19:04 ` Hemmann, Volker Armin
2006-05-26 19:28 ` Alexander Skwar
2006-05-26 22:25 ` Hemmann, Volker Armin
2006-05-26 22:43 ` Neil Bothwick
2006-05-27 0:15 ` Hemmann, Volker Armin
2006-05-27 6:16 ` Alexander Skwar [this message]
2006-05-27 7:58 ` Neil Bothwick
2006-05-27 8:36 ` Steven Susbauer
2006-05-27 8:37 ` Alexander Skwar
2006-05-25 23:41 ` Teresa and Dale
2006-05-25 23:51 ` Iain Buchanan
2006-05-26 4:33 ` Lord Sauron
2006-05-26 7:28 ` Neil Bothwick
[not found] ` <20060526131947.7354f200@lx-arnau.pic.es>
2006-05-26 13:48 ` Alexander Skwar
2006-05-26 4:00 ` Ryan Tandy
2006-05-25 19:44 ` [gentoo-user] " Daniel da Veiga
2006-05-25 19:59 ` [gentoo-user] " Thomas Kirchner
2006-05-26 4:45 ` Lord Sauron
2006-05-29 1:26 ` [gentoo-user] " Thomas Kirchner
2006-05-29 20:55 ` Lord Sauron
2006-05-29 22:26 ` Bo Ørsted Andresen
2006-05-25 20:25 ` [gentoo-user] " Steven Susbauer
2006-05-25 20:33 ` Daniel da Veiga
2006-05-25 21:07 ` Neil Bothwick
2006-05-25 21:20 ` Daniel da Veiga
2006-05-25 23:56 ` Iain Buchanan
2006-05-26 2:50 ` Daniel da Veiga
2006-05-26 3:58 ` Iain Buchanan
2006-05-26 17:00 ` Lord Sauron
2006-05-26 2:40 ` Steven Susbauer
2006-05-26 2:51 ` Daniel da Veiga
2006-05-26 4:00 ` Richard Fish
2006-05-26 4:42 ` Lord Sauron
2006-05-26 7:55 ` leszek
2006-05-26 8:15 ` leszek
2006-05-26 17:02 ` Lord Sauron
2006-05-26 19:23 ` Neil Bothwick
2006-05-27 11:40 ` Iain Buchanan
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=4477EEA2.4060108@mid.email-server.info \
--to=listen@alexander.skwar.name \
--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