On Thu, Jun 4, 2020 at 3:03 PM Dominique Corbex
wrote:
> On Thu, 4 Jun 2020 17:27:22 +0200
> yvand wrote:
>
> > Is it possible to import my module
> > again with old osis2mod version (if the correction takes time).
>
> Should be a little bit hard to find a running 2893 copy as:
>
> $ svn blame -
On Thu, 4 Jun 2020 17:27:22 +0200
yvand wrote:
> Is it possible to import my module
> again with old osis2mod version (if the correction takes time).
Should be a little bit hard to find a running 2893 copy as:
$ svn blame -v osis2mod.cpp | awk '{print $1, $3}'| sort | uniq
lists:
2893 2013-0
Can somebody confirm this bug?
Shall I fill a bug report somewhere? Is it possible to import my module
again with old osis2mod version (if the correction takes time).
--yvand
Le 01/06/2020 à 22:40, John Dudeck a écrit :
This sounds like a problem with (at least the Windows version of) the
o
I just tried with MSE stopped. It made no difference at all.
David
Sent from ProtonMail Mobile
On Wed, Jun 3, 2020 at 22:23, Greg Hellings wrote:
> On Wed, Jun 3, 2020, 15:41 David Haslam wrote:
>
>> The only AV that I use is Windows Security Essentials.
>> This has never caused me any issue
