public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Andrey Repin <anrdaemon@yandex.ru>
To: Duncan Roe <duncan_roe@optusnet.com.au>, cygwin@cygwin.com
Subject: Re: Command line processing in dcrt0.cc does not match Microsoft parsing rules
Date: Mon, 09 Sep 2019 19:44:00 -0000	[thread overview]
Message-ID: <504917608.20190909215627@yandex.ru> (raw)
In-Reply-To: <20190909182654.GA12686@dimstar.local.net>

Greetings, Duncan Roe!

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

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

Cygwin uses Git. Just not GitHub.
The question was to manage ISSUES, though.
And the answer is, this list was working just fine for the purpose so far.
There's no pressing need to change that, last I heard.


-- 
With best regards,
Andrey Repin
Monday, September 9, 2019 21:55:23

Sorry for my terrible english...


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

  reply	other threads:[~2019-09-09 19:05 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-08-30 19:31 Stephen Provine via cygwin
2019-08-30 20:53 ` Brian Inglis
2019-08-30 21:21 ` Stephen Provine via cygwin
2019-08-31  4:18   ` Brian Inglis
2019-09-03 16:38   ` Stephen Provine via cygwin
2019-09-04 16:20     ` Brian Inglis
2019-09-04 23:46     ` Stephen Provine via cygwin
2019-09-05  5:29       ` Brian Inglis
2019-09-05 18:31       ` Stephen Provine via cygwin
2019-09-05 19:05         ` Eric Blake
2019-09-05 22:01         ` Stephen Provine via cygwin
2019-09-05 22:46           ` Eric Blake
2019-09-05 23:45           ` Stephen Provine via cygwin
2019-09-06  0:46             ` Steven Penny
2019-09-06  1:26             ` Eric Blake
2019-09-06  6:20             ` Stephen Provine via cygwin
2019-09-07 21:50           ` Brian Inglis
2019-09-07 12:05         ` Andrey Repin
2019-09-07 12:20           ` Andrey Repin
2019-09-09 16:47           ` Stephen Provine via cygwin
2019-09-09 16:57             ` Stephen Provine via cygwin
2019-09-09 17:11               ` Eric Blake
2019-09-09 19:05                 ` Duncan Roe
2019-09-09 19:44                   ` Andrey Repin [this message]
2019-09-10 12:43                   ` Brian Inglis

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=504917608.20190909215627@yandex.ru \
    --to=anrdaemon@yandex.ru \
    --cc=cygwin@cygwin.com \
    --cc=duncan_roe@optusnet.com.au \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).