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 upd
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
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?
I did not get any response to my last questions, so I hope this patch is
enough.
Any thought about my other arguments?
Federico
On 5/17/20 7:54 PM, Federico Kircheis wrote:
Thank you for the feedback.
This patch is clearly not limited to the protection of data, as it
quotes variables that c
Thank you for the feedback.
This patch is clearly not limited to the protection of data, as it
quotes variables that could in no way contain a space or have anything
to do with file paths.
Could you please point me to which variables are unrelated to files.
AFAIK i quoted files and arguments
On Tue, 2020-05-12 at 16:59 +0200, Federico Kircheis wrote:
> On 10/14/19 10:55 AM, Federico Kircheis wrote:
> > On 13/10/2019 18.41, Achim Gratz wrote:
> > > Federico Kircheis writes:
> > > > I've sent the patches the 14.07.19, unfortunately I still got no answer.
> > >
> > > The cygport maintain
On 10/14/19 10:55 AM, Federico Kircheis wrote:
On 13/10/2019 18.41, Achim Gratz wrote:
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 t
On Mon., Oct. 14, 2019, 02:55 Federico Kircheis, <> wrote:
> On 13/10/2019 18.41, Achim Gratz wrote:
> > 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
On 13/10/2019 18.41, Achim Gratz wrote:
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 change
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 wor
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 w
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
Hello,
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
13 matches
Mail list logo
