> On 16/07/2023 20:32, ASSI via Cygwin-apps wrote:
> > Jon Turney via Cygwin-apps writes:
> >> The warning (error if RESTRICT=case_insensitive) should occur for all
> >> commands, not just prep.
> >
> > OK.
> >
> >> How about the attached.
> >
> > Looks promising.
>
> Ok. I made a cygport
On 23/07/2023 20:13, ASSI via Cygwin-apps wrote:
Jon Turney via Cygwin-apps writes:
Ok. I made a cygport 0.36.6 release with this change.
Thanks. You haven't tagged that release on GitHub yet it seems.
The authoritative upstream is
https://cygwin.com/git/cygwin-apps/cygport.git, which
Jon Turney via Cygwin-apps writes:
> Ok. I made a cygport 0.36.6 release with this change.
Thanks. You haven't tagged that release on GitHub yet it seems.
Regards,
Achim.
--
+<[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]>+
Waldorf MIDI Implementation & additional
On 16/07/2023 20:32, ASSI via Cygwin-apps wrote:
Jon Turney via Cygwin-apps writes:
The warning (error if RESTRICT=case_insensitive) should occur for all
commands, not just prep.
OK.
How about the attached.
Looks promising.
Ok. I made a cygport 0.36.6 release with this change.
Please
Jon Turney via Cygwin-apps writes:
> The warning (error if RESTRICT=case_insensitive) should occur for all
> commands, not just prep.
OK.
> How about the attached.
Looks promising.
> Even then, it should only be modifying every directory, not every file.
Run strace on "chattr -r +C ." and see
On 08/07/2023 15:22, ASSI via Cygwin-apps wrote:
Jon Turney via Cygwin-apps writes:
So, the idea here is that we try to ensure it's on, at least for the
working directory.
That IMHO should only be done when the working directory is created, but
not retroactively applied to an existing
Jon Turney via Cygwin-apps writes:
> So, the idea here is that we try to ensure it's on, at least for the
> working directory.
That IMHO should only be done when the working directory is created, but
not retroactively applied to an existing workdir.
> Skipping it when 'finish' is used isn't
> On 06/07/2023 18:36, Andrew Schulman via Cygwin-apps wrote:
> >> Recently I noticed that `cygport finish` has become really slow on some of
> >> my
> >> package source trees. After I run for example
> >>
> >> cygport libargp.cygport finish
> >>
> >> it waits for about 5 minutes without any
On 06/07/2023 17:18, Brian Inglis via Cygwin-apps wrote:
On 2023-07-06 06:19, Andrew Schulman via Cygwin-apps wrote:
Recently I noticed that `cygport finish` has become really slow on
some of my
package source trees. After I run for example
cygport libargp.cygport finish
it waits for about 5
On 06/07/2023 18:36, Andrew Schulman via Cygwin-apps wrote:
Recently I noticed that `cygport finish` has become really slow on some of my
package source trees. After I run for example
cygport libargp.cygport finish
it waits for about 5 minutes without any message to the console, before the
> Recently I noticed that `cygport finish` has become really slow on some of my
> package source trees. After I run for example
>
> cygport libargp.cygport finish
>
> it waits for about 5 minutes without any message to the console, before the
> first "Removing work directory" message appears.
>
On 2023-07-06 06:19, Andrew Schulman via Cygwin-apps wrote:
Recently I noticed that `cygport finish` has become really slow on some of my
package source trees. After I run for example
cygport libargp.cygport finish
it waits for about 5 minutes without any message to the console, before the
Recently I noticed that `cygport finish` has become really slow on some of my
package source trees. After I run for example
cygport libargp.cygport finish
it waits for about 5 minutes without any message to the console, before the
first "Removing work directory" message appears.
pstree shows
13 matches
Mail list logo
