X-Recipient: archive-cygwin AT delorie DOT com 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= DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; 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; s=default; bh=DVf8vBrf UpFUutZMyNakmG6t780=; b=YaS6M5S0aXnc0KVC5CfQAlKANvCaFzn+7t5y6//x tO09ZGhLJzk/RZaSpk3hv6VrQJU+m4ocbzWp2z9fTt/ZPngfC0VBTPUYQreRCstw 57P9MFkc5O+z2mr8n7iQesio6RD/2RIvd3kJnz5ZLhTvL1soOsO5Lm7fyrwj6zbV uck= Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm List-Id: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner AT cygwin DOT com Mail-Followup-To: cygwin AT cygwin DOT com Delivered-To: mailing list cygwin AT cygwin DOT com Authentication-Results: sourceware.org; auth=none X-Virus-Found: No X-Spam-SWARE-Status: No, score=-2.2 required=5.0 tests=AWL,BAYES_00,FREEMAIL_FROM,RCVD_IN_DNSWL_LOW,SPF_PASS autolearn=ham version=3.3.2 X-HELO: mail-yk0-f172.google.com MIME-Version: 1.0 X-Received: by 10.236.110.77 with SMTP id t53mr11530851yhg.78.1397019849385; Tue, 08 Apr 2014 22:04:09 -0700 (PDT) In-Reply-To: <20140409032833.GA2351@ednor.casa.cgf.cx> References: <5F8AAC04F9616747BC4CC0E803D5907D0C8B4372 AT MLBXv04 DOT nih DOT gov> <20140408090129 DOT GC28755 AT calimero DOT vinschen DOT de> <6CF2FC1279D0844C9357664DC5A08BA2464FF5 AT MLBXV06 DOT nih DOT gov> <5F8AAC04F9616747BC4CC0E803D5907D0C8B85C2 AT MLBXv04 DOT nih DOT gov> <20140408152118 DOT GB4595 AT ednor DOT casa DOT cgf DOT cx> <5344236E DOT 8020503 AT aol DOT com> <20140408164902 DOT GD5812 AT ednor DOT casa DOT cgf DOT cx> <5F8AAC04F9616747BC4CC0E803D5907D0C8B89AF AT MLBXv04 DOT nih DOT gov> <20140408181301 DOT GD2731 AT ednor DOT casa DOT cgf DOT cx> <20140409032833 DOT GA2351 AT ednor DOT casa DOT cgf DOT cx> Date: Wed, 9 Apr 2014 00:04:09 -0500 Message-ID: Subject: Re: We need steenking patches (Re: Cygwin kill utility...) From: Steven Penny To: cygwin AT cygwin DOT com Content-Type: text/plain; charset=ISO-8859-1 X-IsSubscribed: yes 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