DomainKey-Signature: a=rsa-sha1; c=nofws; d=sourceware.org; h=list-id
	:list-unsubscribe:list-subscribe:list-archive:list-post
	:list-help:sender:mime-version:in-reply-to:references:date
	:message-id:subject:from:to:content-type; q=dns; s=default; b=QY
	BNX5Ab4+fQToxLRjAIPMc4S/KTqKYetBsoUeFni7hXxNORn42VjNIOmLxNSP/o6A
	gJ/E8qh8n3BhqkKwGMslU1+Og/u1IyzJrGxD//PHt5ASIhZnkAx0jpMbTLWUWmSa
	YMFjKLMujAbo9SLyHBoVogVf4DZBj34znDZinvpFc=
Mailing-List: contact cygwin-help@cygwin.com; run by ezmlm
Sender: cygwin-owner@cygwin.com
Mail-Followup-To: cygwin@cygwin.com
MIME-Version: 1.0
In-Reply-To: <20140409032833.GA2351@ednor.casa.cgf.cx>
References: <5F8AAC04F9616747BC4CC0E803D5907D0C8B4372@MLBXv04.nih.gov>	<20140408090129.GC28755@calimero.vinschen.de>	<6CF2FC1279D0844C9357664DC5A08BA2464FF5@MLBXV06.nih.gov>	<5F8AAC04F9616747BC4CC0E803D5907D0C8B85C2@MLBXv04.nih.gov>	<20140408152118.GB4595@ednor.casa.cgf.cx>	<5344236E.8020503@aol.com>	<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>
Date: Wed, 9 Apr 2014 00:04:09 -0500
Message-ID: <CAAXzdLUk3L3zRcGoLmb=GM-rnF7K8Y=fqNA8n9gfgVhja5TL2Q@mail.gmail.com>
Subject: Re: We need steenking patches (Re: Cygwin kill utility...)
From: Steven Penny <svnpenn@gmail.com>
To: cygwin@cygwin.com
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Apr 8, 2014 at 10:28 PM, Christopher Faylor wrote:
> Instructions on how to check out the source are available at the cygwin web
> site, just like they are at every open source site.  Go to the cygwin web
> page and look to the left.  You'll see "Contributing" and "Source in CVS".
> Both lead you to instructions.  "Contributing" is intended to help with
> providing patches.  "Source in CVS" is obvious.

I dont think you "get" my and perhaps other people's workflow. It goes like this

1. discover something that isnt working
2. go to web repo
3. search existing issues
4. search current codebase, online, to find offending file/line
5. if it looks like something I can fix then clone/checkout

Notice a checkout is not even done until step 5, with steps 1-4 all being done
through web interface. This is important. Your users (read: potential devs)
should not have to do a clone just to see the problem in the code.

Of course once I reach step 5 things are much smoother because you can work with
the local codebase. However if you cannot offer steps 1-4 then you are only
"tying one hand behind your back" and all the whining on the mailing list wont
fix that.

--
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