On Wednesday, January 06, 2016 10:30:52 AM Ben Cooksley wrote:
> On Wed, Jan 6, 2016 at 3:17 AM, Kevin Funk wrote:
> > On Wednesday, December 30, 2015 12:57:23 PM Ben Cooksley wrote:
> >> On Tue, Dec 29, 2015 at 11:16 PM, Kevin Funk wrote:
> >> > On Tuesday, December 29, 2015 10:39:01 PM Ben Cook
On Wed, Jan 6, 2016 at 3:17 AM, Kevin Funk wrote:
> On Wednesday, December 30, 2015 12:57:23 PM Ben Cooksley wrote:
>> On Tue, Dec 29, 2015 at 11:16 PM, Kevin Funk wrote:
>> > On Tuesday, December 29, 2015 10:39:01 PM Ben Cooksley wrote:
>> >> On Tue, Dec 29, 2015 at 7:59 AM, Lydia Pintscher wro
On Wednesday, December 30, 2015 12:57:23 PM Ben Cooksley wrote:
> On Tue, Dec 29, 2015 at 11:16 PM, Kevin Funk wrote:
> > On Tuesday, December 29, 2015 10:39:01 PM Ben Cooksley wrote:
> >> On Tue, Dec 29, 2015 at 7:59 AM, Lydia Pintscher wrote:
> >> > On Sun, Dec 27, 2015 at 12:35 PM, Ben Cooksle
On Tue, Dec 29, 2015 at 11:16 PM, Kevin Funk wrote:
> On Tuesday, December 29, 2015 10:39:01 PM Ben Cooksley wrote:
>> On Tue, Dec 29, 2015 at 7:59 AM, Lydia Pintscher wrote:
>> > On Sun, Dec 27, 2015 at 12:35 PM, Ben Cooksley wrote:
>> >>> Is there some place where search engines can easily ind
On Tuesday, December 29, 2015 10:39:01 PM Ben Cooksley wrote:
> On Tue, Dec 29, 2015 at 7:59 AM, Lydia Pintscher wrote:
> > On Sun, Dec 27, 2015 at 12:35 PM, Ben Cooksley wrote:
> >>> Is there some place where search engines can easily index our source
> >>> code or are we shooting ourselves in t
On Tuesday, December 29, 2015 10:39:01 PM Ben Cooksley wrote:
> On Tue, Dec 29, 2015 at 7:59 AM, Lydia Pintscher wrote:
> > On Sun, Dec 27, 2015 at 12:35 PM, Ben Cooksley wrote:
> >>> Is there some place where search engines can easily index our source
> >>> code or are we shooting ourselves in t
On Tue, Dec 29, 2015 at 7:59 AM, Lydia Pintscher wrote:
> On Sun, Dec 27, 2015 at 12:35 PM, Ben Cooksley wrote:
>>> Is there some place where search engines can easily index our source
>>> code or are we shooting ourselves in the foot here?
>>
>> We could probably make it available by publishing
On Montag, 28. Dezember 2015 18:09:32 CEST, Kevin Funk wrote:
Are you aware that not even every KDE developer knows about
LXR? I constantly have to tell people about it.
Yes, and I'm as well aware of the "if it's not in google, it doesn't exist"
phenomenon, BUT: that's not gonna work.
If yo
On Sun, Dec 27, 2015 at 12:35 PM, Ben Cooksley wrote:
>> Is there some place where search engines can easily index our source
>> code or are we shooting ourselves in the foot here?
>
> We could probably make it available by publishing the source trees
> used by LXR / EBN.
> This would only have th
On Monday, December 28, 2015 04:37:47 PM Thomas Lübking wrote:
> On Montag, 28. Dezember 2015 11:35:23 CEST, Albert Vaca wrote:
> > Lxr can't search across every open source project in the world, so that's
> > a
> > point for Google.
>
> Presuming google could, why would I. Or anyone?
> I dig for
On Monday, December 28, 2015 04:37:47 PM Thomas Lübking wrote:
> On Montag, 28. Dezember 2015 11:35:23 CEST, Albert Vaca wrote:
> > Lxr can't search across every open source project in the world, so that's
> > a
> > point for Google.
>
> Presuming google could, why would I. Or anyone?
> I dig for
El Monday 28 December 2015, a les 16:37:47, Thomas Lübking va escriure:
> On Montag, 28. Dezember 2015 11:35:23 CEST, Albert Vaca wrote:
> > Lxr can't search across every open source project in the world, so that's
> > a
> > point for Google.
>
> Presuming google could, why would I. Or anyone?
Yo
On Montag, 28. Dezember 2015 11:35:23 CEST, Albert Vaca wrote:
Lxr can't search across every open source project in the world, so that's a
point for Google.
Presuming google could, why would I. Or anyone?
I dig for certain variables or strings in specific code, but why would I look for m_foo or
Lxr can't search across every open source project in the world, so that's a
point for Google.
>> Visit http://mail.kde.org/mailman/listinfo/kde-devel#unsub to unsubscribe <<
On Sonntag, 27. Dezember 2015 12:35:51 CEST, Ben Cooksley wrote:
We could probably make it available by publishing the source trees
used by LXR / EBN.
Because if it's not in google, it doesn't exist?
We've lxr which is a dedicated and *far* superior way to search our code, so what exactly
i
On Mon, Dec 28, 2015 at 12:15 AM, Lydia Pintscher wrote:
> On Sun, Dec 27, 2015 at 12:08 PM, Ben Cooksley wrote:
>> On Sun, Dec 27, 2015 at 11:53 PM, Ashish Bansal
>> wrote:
>>> Hi everyone,
>>
>> Hi Ashish,
>>
>>>
>>> "quickgit.kde.org" contains robots.txt[0] which is disallowing search
>>> eng
On Sun, Dec 27, 2015 at 12:08 PM, Ben Cooksley wrote:
> On Sun, Dec 27, 2015 at 11:53 PM, Ashish Bansal
> wrote:
>> Hi everyone,
>
> Hi Ashish,
>
>>
>> "quickgit.kde.org" contains robots.txt[0] which is disallowing search
>> engines to fetch the project repos. I just wanted to know if this is
>>
On Sun, Dec 27, 2015 at 11:53 PM, Ashish Bansal
wrote:
> Hi everyone,
Hi Ashish,
>
> "quickgit.kde.org" contains robots.txt[0] which is disallowing search
> engines to fetch the project repos. I just wanted to know if this is
> intentional or not?
>
> If I recall correctly, mirror of kde reposit
Hi everyone,
"quickgit.kde.org" contains robots.txt[0] which is disallowing search
engines to fetch the project repos. I just wanted to know if this is
intentional or not?
If I recall correctly, mirror of kde repositories on github was created
just because it wasn't being indexed by the search en
19 matches
Mail list logo
