From: Neil Bothwick <neil@digimed.co.uk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] sane-backends
Date: Sun, 17 Apr 2011 15:56:32 +0100 [thread overview]
Message-ID: <20110417155632.5641e352@digimed.co.uk> (raw)
In-Reply-To: <4DAA25AE.4070904@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
On Sat, 16 Apr 2011 18:26:38 -0500, Dale wrote:
> Some put them in the overlay to test then move them over to the tree a
> bit later if there are no problems or weird dependency problems.
>
> I think there is a fancy command to get that info but can't recall it
> at the moment. I bet someone will post it tho. ;-)
eix-remote update
Run this after an emerge --sync && eix-update and eix will index the
overlays you don't use as well as the ones you do.
--
Neil Bothwick
"Bad dog! Leave that wire alone.....click.....###@*##....NO TERRIER
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2011-04-17 15:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-16 22:52 [gentoo-user] sane-backends Michael George
2011-04-16 23:26 ` Dale
2011-04-16 23:41 ` Dale
2011-04-17 14:56 ` Neil Bothwick [this message]
2011-04-17 8:08 ` Kfir Lavi
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=20110417155632.5641e352@digimed.co.uk \
--to=neil@digimed.co.uk \
--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