DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:date:from:to:subject:message-id:reply-to
	:references:mime-version:content-type:in-reply-to; q=dns; s=
	default; b=wXpsGKL58uzrnKgr2yy3x5eg+zrcXWITWd6IBYB0/ScJdk7henavN
	ORMI3+Ui4CvT1hsn8ILtsKZ/OBODr3joU+gKq5LIbvJjvEd2wyDy8Z9Qv1fjgHZ7
	IvT/LDHwsNUjUxgKyWNpwBFj7IQzAl1x76uUwFuBqTHND+5G66Bn7M=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
Date: Wed, 9 Apr 2014 13:13:31 -0400
From: Christopher Faylor <cgf-use-the-mailinglist-please@cygwin.com>
To: cygwin@cygwin.com
Subject: Re: We need steenking patches (Re: Cygwin kill utility...)
Message-ID: <20140409171331.GB6319@ednor.casa.cgf.cx>
Reply-To: cygwin@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
References: <20140408164902.GD5812@ednor.casa.cgf.cx> <5F8AAC04F9616747BC4CC0E803D5907D0C8B89AF@MLBXv04.nih.gov> <20140408181301.GD2731@ednor.casa.cgf.cx> <CAAXzdLUJaQ3ap06EPD51ua45d7vqmaPanCZRo9CZDPKmMfm5=w@mail.gmail.com> <20140409032833.GA2351@ednor.casa.cgf.cx> <CAAXzdLUk3L3zRcGoLmb=GM-rnF7K8Y=fqNA8n9gfgVhja5TL2Q@mail.gmail.com> <20140409055117.GA1878@ednor.casa.cgf.cx> <CAAXzdLXxAnB0JYHuvJj44ZAT=Uc-G12Xt+xsirnmiPBkOJ4U-w@mail.gmail.com> <53457A4C.1050104@etr-usa.com> <CAAXzdLVfbuWujEXQXsZY2_puq7JkEmJemeEZJ+DXhdQHb2wQLA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <CAAXzdLVfbuWujEXQXsZY2_puq7JkEmJemeEZJ+DXhdQHb2wQLA@mail.gmail.com>
User-Agent: Mutt/1.5.20 (2009-06-14)

On Wed, Apr 09, 2014 at 12:02:46PM -0500, Steven Penny wrote:
>On Wed, Apr 9, 2014 at 11:37 AM, Christopher Faylor wrote:
>> I'll once again point out that gdb, binutils, and gcc seem to get by
>> just fine without this.  And, maybe I missed something, but I don't see
>> search on sourceforge.net either.  Given that, I don't see how this can
>> be a huge barrier to entry.
>
>Noted. However this is an irrelevant conclusion. The fact that they are
>successful does not mean Cygwin wont benefit from a search function.

You clipped the part where I said "I'll see what I can do" and then offered
a followup as to why it may not be a good idea to have a search function.

I didn't say that a search function wouldn't be useful.  I said that it
can't be a huge barrier to entry given the fact that many popular
projects don't have that kind of functionality.

>On Wed, Apr 9, 2014 at 11:50 AM, Warren Young wrote:
>> If you think web code repository searching and a public bug tracker are
>> primary barriers to contribution, you aren't being honest with yourself.
>> They are nice, but not necessary.
>
>I am honest with myself. I, as everyone have limited time. I will not waste my
>time with an archaic system and maintainers who fail to see the light of day
>when there are better ways I can spend my time, example
>
>  http://github.com/stars/svnpenn

It's possible that a site like github has more bandwidth and compute
power than sourceware.org and doesn't have to worry about bogging down
the system with malicious search attacks.  We, unfortunately, do.  So,
while it is possible to turn on searches, it seems like I'd have to
personally take some time to fixing the viewvc code to mitigate any
damage from using searches.  That is more effort than I'm willing to go
to on one person's claim that this functionality is vitally necessary.

cgf

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple