From: Achim Gratz <Stromeko@nexgo.de>
To: cygwin-apps@cygwin.com
Subject: Re: cygport development
Date: Sun, 13 Oct 2019 16:41:00 -0000 [thread overview]
Message-ID: <871rvgwqbc.fsf@Rainer.invalid> (raw)
In-Reply-To: <97e449ba-2c23-a110-ce95-850394b398cf@gmail.com> (Federico Kircheis's message of "Sat, 28 Sep 2019 13:56:40 +0200")
Federico Kircheis writes:
> I've sent the patches the 14.07.19, unfortunately I still got no answer.
The cygport maintainer is rather busy with non-Cygwin related work these
days, I suppose. Anyway, one of the questions I have is why you need
these changes. Most build systems do not actually work when they
encounter a path with spaces if they use make under the hood, so fixing
cygport to grok such path locations isn't getting you much further I'd
think. Can you explain?
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Wavetables for the Waldorf Blofeld:
http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
next prev parent reply other threads:[~2019-10-13 16:41 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 ` cygport development Federico Kircheis
2019-10-13 16:41 ` Achim Gratz [this message]
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=871rvgwqbc.fsf@Rainer.invalid \
--to=stromeko@nexgo.de \
--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).