Bin Meng writes:
> From: Bin Meng
>
> At present winsymlinks is set to 'nativestrict', and its behavior is:
>
> a) if native symlinks are enabled and exists, creates
> as a native Windows symlink;
> b) else if native symlinks are not enabled or if does
> not exist, 'ln -s' fai
On 19/07/2022 18.12, Bin Meng wrote:
From: Bin Meng
At present winsymlinks is set to 'nativestrict', and its behavior is:
a) if native symlinks are enabled and exists, creates
as a native Windows symlink;
b) else if native symlinks are not enabled or if does
not exist, 'ln
On Mon, Jul 25, 2022 at 9:24 AM Bin Meng wrote:
>
> On Wed, Jul 20, 2022 at 12:12 AM Bin Meng wrote:
> >
> > From: Bin Meng
> >
> > At present winsymlinks is set to 'nativestrict', and its behavior is:
> >
> > a) if native symlinks are enabled and exists, creates
> > as a native Windows
On Wed, Jul 20, 2022 at 12:12 AM Bin Meng wrote:
>
> From: Bin Meng
>
> At present winsymlinks is set to 'nativestrict', and its behavior is:
>
> a) if native symlinks are enabled and exists, creates
> as a native Windows symlink;
> b) else if native symlinks are not enabled or if doe
From: Bin Meng
At present winsymlinks is set to 'nativestrict', and its behavior is:
a) if native symlinks are enabled and exists, creates
as a native Windows symlink;
b) else if native symlinks are not enabled or if does
not exist, 'ln -s' fails.
This causes the following erro
