public inbox for cygwin-apps@cygwin.com
 help / color / mirror / Atom feed
From: Federico Kircheis <federico.kircheis@gmail.com>
To: cygwin-apps@cygwin.com
Subject: Re: cygport development
Date: Sat, 6 Nov 2021 15:53:00 +0100	[thread overview]
Message-ID: <158d59a2-face-ae2e-4730-b397d0b161e3@gmail.com> (raw)
In-Reply-To: <2670125d-18a8-0d29-4bc6-a9fb7821875b@gmail.com>


On 29/06/2020 18.04, Federico Kircheis wrote:
> On 6/12/20 9:55 AM, Federico Kircheis wrote:
>> On May 29, 2020 4:38:53 AM UTC, Federico Kircheis wrote:
>>> I did not get any response to my last questions, so I hope this patch
>>> is
>>> enough.
>>>
>>> Any thought about my other arguments?
>>>
>>> Federico
>> Ping.
>>
>> Any updates or comments?
>>
>> Is the patch ok?
>>
> 
> Ping



I know it's been a while, I still would like cygport to avoid messing up 
unrelated directories.

Are there any disadvantage stopping when cd fails?
I did not get any feedback.

AFAIK my patch has not been integrated and still applies to current master.

Best

Federico

      reply	other threads:[~2021-11-06 14:57 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
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 [this message]

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=158d59a2-face-ae2e-4730-b397d0b161e3@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).