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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; q=dns; s=default; b=N5WyW4cNz6z/vYDN
	6+EmTkQ5zSvTDeBx273LqPjTPnUtaZXiEvJXeYmFwMHBCaUTv9LN6n3BQCpi6Wmt
	T+CsLVPvS0eA5yNku+BIXolmWtAdSEPRCYcvLe1VDqGRykilfmhQcdBd3yJJprbb
	7qJ30V4gxOAuUbIqIxLLDSRWaTs=
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:reply-to:subject:to:references:from:message-id
	:date:mime-version:in-reply-to:content-type
	:content-transfer-encoding; s=default; bh=NPphoOpbCIzxcrMVG1k1W5
	332dY=; b=t+g+9FwUdpHwc4RJRWlnj6OIvLoe8ZbLzXfxBtkrRaOrVvMqui6cHl
	RUGl6zzzeaUBUSf5su+KEt/S4esa4yv9qVxIylBYuZzi63MwZO3rUQVaAQPyHT6u
	TvMj1Y51Yg8z5jllIBEi26Gg0EW4fj8g7gxlmS19qDgvXT220i+VY=
Mailing-List: contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Id: <cygwin.cygwin.com>
List-Subscribe: <mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive: <http://sourceware.org/ml/cygwin/>
List-Post: <mailto:cygwin AT cygwin DOT com>
List-Help: <mailto:cygwin-help AT cygwin DOT com>, <http://sourceware.org/ml/#faqs>
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-Spam-SWARE-Status: No, score=-2.5 required=5.0 tests=AWL,BAYES_00,KAM_SHORT,RCVD_IN_DNSWL_NONE autolearn=ham version=3.3.1 spammy=H*Ad:D*ca, contributions, HX-Languages-Length:1983
X-HELO: smtp-out-so.shaw.ca
Reply-To: Brian DOT Inglis AT SystematicSw DOT ab DOT ca
Subject: Re: Command line processing in dcrt0.cc does not match Microsoft parsing rules
To: cygwin AT cygwin DOT com
References: <MWHPR21MB08452919F35B1B0C5F0EB4DCB9BD0 AT MWHPR21MB0845 DOT namprd21 DOT prod DOT outlook DOT com> <MWHPR21MB0845F78385792965A94E0CD9B9BD0 AT MWHPR21MB0845 DOT namprd21 DOT prod DOT outlook DOT com> <MWHPR21MB084508155AB621C7AD81309CB9B90 AT MWHPR21MB0845 DOT namprd21 DOT prod DOT outlook DOT com> <MWHPR21MB08456D9F03AF8BD450E6AB2EB9B80 AT MWHPR21MB0845 DOT namprd21 DOT prod DOT outlook DOT com> <MWHPR21MB0845282E7582DC95ADF0F140B9BB0 AT MWHPR21MB0845 DOT namprd21 DOT prod DOT outlook DOT com> <135817606 DOT 20190906233445 AT yandex DOT ru> <CY4PR21MB0838765A912890C93D4F223DB9B70 AT CY4PR21MB0838 DOT namprd21 DOT prod DOT outlook DOT com> <CY4PR21MB08388C6AF65D78D5FE3E68DDB9B70 AT CY4PR21MB0838 DOT namprd21 DOT prod DOT outlook DOT com> <cd9940c6-8eec-8cc9-7377-8428f3b220fc AT redhat DOT com> <20190909182654 DOT GA12686 AT dimstar DOT local DOT net>
From: Brian Inglis <Brian DOT Inglis AT SystematicSw DOT ab DOT ca>
Openpgp: preference=signencrypt
Message-ID: <b93e255f-79b0-7edb-ae22-cb4149d2bff4@SystematicSw.ab.ca>
Date: Mon, 9 Sep 2019 13:44:35 -0600
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.0
MIME-Version: 1.0
In-Reply-To: <20190909182654.GA12686@dimstar.local.net>
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-IsSubscribed: yes

On 2019-09-09 12:26, Duncan Roe wrote:
> On Mon, Sep 09, 2019 at 11:57:21AM -0500, Eric Blake wrote:
>> On 9/9/19 11:47 AM, Stephen Provine via cygwin wrote:
>>> Argh, my mistake about top posting again. My email client does not help me
>>> with this by default and I have to manually construct quoting of previous
>>> responses and delete what shouldn't be there (and missed it again). If there's
>>> any way for someone to delete my previous message from the archive, please do.
>>>
>>> Why doesn't Cygwin utilize Github or something else more modern to manage issues?
>>
>> Just because it is "modern" does not necessarily make it better.
>>
>> https://www.gnu.org/software/repo-criteria-evaluation.en.html
>>
>> ranks github as worse than gitlab, in part because there is no way to
>> use the full power of github without surrendering to the use of non-free
>> software.

And it's now owned by a proprietary vendor without any roots in open source.

> No problems with that. I think though, that the OP's point was to use *git*
> (wherever the repo may be).

The core code repo is in git on sourceware.org alias cygwin.com:
https://cygwin.com/git/gitweb.cgi?p=newlib-cygwin.git

The patch and commit messages, and ChangeLog and NEWS files often contain
references to the OPs reporting problems.

There are no issue or bug handling components for git.

There are bugzillas that have been write-only since about 2012:
https://cygwin.com/bugzilla/describecomponents.cgi?product=cygwin
if you report there just remember to email this list with a link to the bug.

There is also savannah.nongnu.org which might be usable, as most
non-GPL/AGPL/LGPL contributions, are BSD licensed to allow modification for
proprietary uses.

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.

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