On Sep 29, 2017 7:43 AM, "Andy Goth" wrote:
On 09/28/17 21:34, Scott Robison wrote:
> There is a winsymlink branch I created some time ago. Hasn't been kept
> up to date (I didn't need it, just thought it might be useful for
> feature parity) but I could take a look at
On 09/28/17 21:34, Scott Robison wrote:
There is a winsymlink branch I created some time ago. Hasn't been kept
up to date (I didn't need it, just thought it might be useful for
feature parity) but I could take a look at it if you were interested.
Or you could.
I had a peek. I know Windows NT
On 09/29/17 04:20, Richard Hipp wrote:
On 9/28/17, Andy Goth wrote:
http://fossil-scm.org/index.html/info/8d6bdd1e00cf2cf8
Moved onto a branch: enhanced-symlink
I thought about branching when I checked in, but I decided to stick with
trunk because this can't
On 9/28/17, Andy Goth wrote:
> http://fossil-scm.org/index.html/info/8d6bdd1e00cf2cf8
Moved onto a branch: enhanced-symlink
>
> I added support for a new "l" flag to the "manifest" setting. With this
> flag present, a new file "manifest.symlinks" is automatically
There is a winsymlink branch I created some time ago. Hasn't been kept up
to date (I didn't need it, just thought it might be useful for feature
parity) but I could take a look at it if you were interested. Or you could.
On Sep 28, 2017 7:08 PM, "Andy Goth" wrote:
>
http://fossil-scm.org/index.html/info/8d6bdd1e00cf2cf8
I added support for a new "l" flag to the "manifest" setting. With this
flag present, a new file "manifest.symlinks" is automatically created
and maintained. This file lists all symlinks (not their targets).
I need this feature for a
6 matches
Mail list logo