From: Federico Kircheis <federico.kircheis@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: cygport development
Date: Sat, 28 Sep 2019 11:56:00 -0000 [thread overview]
Message-ID: <97e449ba-2c23-a110-ce95-850394b398cf@gmail.com> (raw)
In-Reply-To: <3501279f-70c8-042c-2e60-2cd315277ae9@SystematicSw.ab.ca>
On 14.07.19 19:10, Brian Inglis wrote:
> On 2019-07-14 07:25, Federico Kircheis wrote:
>> I had the unfortunate idea to execute cygport in a directory that had in it's
>> path at least one whitespace (it's not that uncommon under Windows).
>> Cygport did not report a clear error, and created files at the wrong location.
>> I've posted a patch on github a couple of weeks ago (see
>> https://github.com/cygwinports/cygport/pull/12), but I did not get any feedback.
>> Does the development of cygport take place on github?
>> Should I post my patches somewhere else in order to get them integrated in cygport?
>
> Cygport is a regular Cygwin app used by package maintainers.
> Send here and attach them as text with a git send-email subject and cover letter
> summarising the change and impact (as to cygwin-patches).
>
I've sent the patches the 14.07.19, unfortunately I still got no answer.
I also checked https://github.com/cygwinports/cygport, AFAIK there was
no activity.
Best regards
Federico
next prev parent reply other threads:[~2019-09-28 11:56 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-14 13:25 Federico Kircheis
2019-07-14 17:11 ` Brian Inglis
2019-07-14 19:39 ` [PATCH 1/2] Add support for path with spaces Federico Kircheis
2019-07-14 19:39 ` [PATCH 2/2] Exit in case `cd` fails Federico Kircheis
2019-09-28 11:56 ` Federico Kircheis [this message]
2019-10-13 16:41 ` cygport development Achim Gratz
2019-10-14 8:55 ` Federico Kircheis
2019-10-14 17:15 ` Doug Henderson
2020-05-12 14:59 ` Federico Kircheis
2020-05-15 4:55 ` Yaakov Selkowitz
2020-05-17 17:54 ` Federico Kircheis
2020-05-29 4:38 ` Federico Kircheis
2020-06-12 7:55 ` Federico Kircheis
2020-06-29 16:04 ` Federico Kircheis
2021-11-06 14:53 ` Federico Kircheis
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=97e449ba-2c23-a110-ce95-850394b398cf@gmail.com \
--to=federico.kircheis@gmail.com \
--cc=cygwin-apps@cygwin.com \
/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).