From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.62) (envelope-from ) id 1Gzw3I-0000Mh-4q for garchives@archives.gentoo.org; Thu, 28 Dec 2006 14:16:12 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.8/8.13.8) with SMTP id kBSEE7vL013848; Thu, 28 Dec 2006 14:14:07 GMT Received: from ciao.gmane.org (main.gmane.org [80.91.229.2]) by robin.gentoo.org (8.13.8/8.13.8) with ESMTP id kBSEE63T005357 for ; Thu, 28 Dec 2006 14:14:06 GMT Received: from list by ciao.gmane.org with local (Exim 4.43) id 1Gzw15-00086j-PN for gentoo-amd64@lists.gentoo.org; Thu, 28 Dec 2006 15:13:55 +0100 Received: from ip68-231-13-122.ph.ph.cox.net ([68.231.13.122]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 28 Dec 2006 15:13:55 +0100 Received: from 1i5t5.duncan by ip68-231-13-122.ph.ph.cox.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Thu, 28 Dec 2006 15:13:55 +0100 X-Injected-Via-Gmane: http://gmane.org/ To: gentoo-amd64@lists.gentoo.org From: Duncan <1i5t5.duncan@cox.net> Subject: [gentoo-amd64] Re: problems emerging tclx Date: Thu, 28 Dec 2006 14:13:38 +0000 (UTC) Message-ID: References: <20061227111653.GA32181@brego.pewamo.office> <20061228015743.GA6475@brego.pewamo.office> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-amd64@gentoo.org Reply-to: gentoo-amd64@lists.gentoo.org Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Complaints-To: usenet@sea.gmane.org X-Gmane-NNTP-Posting-Host: ip68-231-13-122.ph.ph.cox.net User-Agent: pan 0.120 (Plate of Shrimp) Sender: news X-Archives-Salt: c10a761b-3446-4234-92e2-6eb905e82d96 X-Archives-Hash: 9309c4d1cbd246020c62f7fea7bc3d9c Michael George posted 20061228015743.GA6475@brego.pewamo.office, excerpted below, on Wed, 27 Dec 2006 20:57:43 -0500: > You are right, I didn't search the gentoo bugs, but I shall in the > future. I didn't know that Google wouldn't grab them... It's not something one would expect, certainly, given that Google knows how to index and can often supply from cache as HTML everything from PDF to MS Word and Excel files. However, each bugzilla installation, certainly the big ones used by the various distributions and all the big projects, tends to be somewhat customized, so Google would need to customize it's bots for each one, and apparently the individual user segments interested in each one are small enough Google hasn't found it worth the trouble to do and maintain. So it's an understandable mis-assumption. Still, think about it. How many bugzilla results have you ever come across in your various Linux info searches? I've certainly not come across that many, if any. It's just that it doesn't occur to folks, since they are used to google indexing virtually /everything/ on the web. I knew I always used bugzilla for that type of searches, not google, but I didn't realize why, until someone happened to explain it in a post such as this one. So anyway, now you (and possibly others on the list) know. =8^) Google's good for a lot of stuff, but not for looking up bugs filed in bugzilla. Neat thing about newsgroups/mailing-lists that way. You ask a question, or read one someone else has asked, and often get answers to questions you didn't even know you had, in the process of getting the answer to the one. =8^) That's one reason I find them so much fun, as I never know what new and useful thing I'm going to learn when I load up the messages. =8^) -- Duncan - List replies preferred. No HTML msgs. "Every nonfree program has a lord, a master -- and if you use the program, he is your master." Richard Stallman -- gentoo-amd64@gentoo.org mailing list