On 8. 2. 2016 9:47, Jan Nijtmans wrote:
> 2016-02-07 19:12 GMT+01:00 David Macek:
>> The reason is to reduce unexpected behavior. In MSYS2, we want to build
>> software as close as
>> reasonably possible to Linux "originals". I can see that the WIN32/CYGWIN
>>
On 7. 2. 2016 15:24, Jan Nijtmans wrote:
> 2016-02-07 14:12 GMT+01:00 David Macek:
>> Hmm. So hopefully he's watching the list.
>
> Yes, I am watching this list. I always build fossil using
> win/Makefile.mingw or win/Makefile.mingw.mistachkin,
> they work fine in the c
build
and work regardless (both globbing and non-ASCII characters in filenames), but
maybe I'm missing something.
Cheers.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
___
fossil-users mailing list
fossil-users@list
on't have anything coherent for you at the moment. Shall we discuss on
IRC, or is it better if I write things down here on the list?
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
___
fossil-users mailing list
fossil-user
I compile Fossil with mingw-w64 in MSYS2. See
<https://github.com/alexpux/mingw-packages/tree/master/mingw-w64-fossil/> for
the build script and a patch (mostly to revert a bunch of Windows-related
nonsense) for v1.33.
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Sig
ked though..
>
> But that should still not account for that same stub to then fail when called
> by fossil either.
Could this be a 32-bit vs. 64-bit issue?
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
___
fossil-u
erpreter.
Does your favorite editor always return -1?
--
David Macek
smime.p7s
Description: S/MIME Cryptographic Signature
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
guess I need to look for a reliable Win7-based stand-alone
> patch utility. Until then, manual editing! :)
What do you mean by stand-alone? I'm inclined to suggest Cygwin/MSYS2 patch,
but I could also look at building/fixing a recent patch with the mingw-w64
toolchain if your patc
On 29. 3. 2015 16:55, Andy Bradford wrote:
> Given that you're using nginx as a proxy, perhaps you need to add
> --baseurl to the fossil server options?
OP mentioned that he tried it.
--
David Macek
smime.p7s
Description: S/MIME Cryptographi
lone as a bare repo and consider it primary. Git should use
hard links for local cloning, so the operation shouldn't be slower than with
Fossil.
Second, there's git-new-workdir. I have not used it, but it seems to exist
exactly for this use case.
<https://github.com/git/git/blob/
Fossil doesn't complain about
permissions anymore.
I'm not sure if chasing every corner case is worth it though, maybe it's better
to give users an option to skip the check.
I posted this before on fossil-dev by mistake, sorry for that.
--
David Macek
smime.p7s
Description: S/MIM
11 matches
Mail list logo
