On 19/02/2017 21:27, Ron W wrote:
>
> Currently there is no one in the Fossil community to run such a "chat
> room".
I know the existence of a ##fossil channel on freenode.net but maybe
it's not official... :)
___
fossil-users mailing list
fossil-use
Hi
There are still inconsistencies in the binary downloads for linux at
fossil's web site.
File fossil-linux-x86-1.37.tar.gz contains a x64 (64-bit) executable.
There seems to be no 32-bit linux executable download.
Could someone please fix that for this and future builds?
Regards
Emil
___
On 2/20/17, Emil Totev wrote:
> Hi
>
> There are still inconsistencies in the binary downloads for linux at
> fossil's web site.
>
> File fossil-linux-x86-1.37.tar.gz contains a x64 (64-bit) executable.
> There seems to be no 32-bit linux executable download.
>
> Could someone please fix that for
I'd vote for x86_64 or amd64 (or even EM64T), but not "x64" (which is
gibberish).
On Mon, 20 Feb 2017, Richard Hipp wrote:
On 2/20/17, Emil Totev wrote:
Hi
There are still inconsistencies in the binary downloads for linux at
fossil's web site.
File fossil-linux-x86-1.37.tar.gz contains a x
Any chance to get the Windows binary as x64 also?
Thanks for Fossil.
On Mon, Feb 20, 2017 at 9:58 AM, Roy Keene wrote:
> I'd vote for x86_64 or amd64 (or even EM64T), but not "x64" (which is
> gibberish).
>
> On Mon, 20 Feb 2017, Richard Hipp wrote:
>
> On 2/20/17, Emil Totev wrote:
>>
>>> Hi
For a report, I wanted to know the longest interval between to
check-ins (not necessarily on the same branch) for a project. In
other words, I wanted to know the longest period of inactivity for a
project. Turns out this is relatively easy to do with Fossil and some
SQL. This message is just to
On 2/20/17, sky5w...@gmail.com wrote:
> Any chance to get the Windows binary as x64 also?
The problem with that (for me at least) is that it is difficult to
compile the OpenSSL library using MSVC. OpenSSL really wants to be
compiled with MinGW. And I only have a 32-bit MingGW compiler. So
(for
On Fri, 17 Feb 2017 00:19:08 -0600
Artur Shepilko wrote:
> To summarize the findings:
> - Sqlite Fossil repo has a number of special cases that do not export
> directly, resulting in "git fast-import" crash.
> - To accomplish the export, one needs to apply the following fixes to
> the __local__
On 20 February 2017 at 15:39, Richard Hipp wrote:
> I don't know if the above has any practical use for most people (or I
> would make it a new URI on the Fossil webserver) but it seems like fun
> and so I thought I would share.
sure!, it serves to document sleep patterns without having to strap
Ah, I see it is somewhat quirky:
https://wiki.openssl.org/index.php/Compilation_and_Installation#W64
Thanks for explaining the Windows x64 gap.
On Mon, Feb 20, 2017 at 10:42 AM, Richard Hipp wrote:
> On 2/20/17, sky5w...@gmail.com wrote:
> > Any chance to get the Windows binary as x64 also?
>
Thus said Richard Hipp on Mon, 20 Feb 2017 07:40:43 -0500:
> I suspect that the Mac and OpenBSD builds are 64-bits too. I suppose
> we could produce 32-bit binaries, but I worry that they would be
> largely untested, since I use 64-bit machines almost exclusively, as I
> suspect most of th
Thus said Richard Hipp on Mon, 20 Feb 2017 10:39:09 -0500:
> Now remind me again, how would you do this in Git? ;-)
To get these kinds of reports I import my Git repositories into Fossil.
:-)
Andy
--
TAI64 timestamp: 400058ab1b40
___
fossil-use
> Subject: Re: [fossil-users] Linux binary downloads
> On 2/20/17, Emil Totev wrote:
>> Hi
>>
>> There are still inconsistencies in the binary downloads for linux at
>> fossil's web site.
>>
>> File fossil-linux-x86-1.37.tar.gz contains a x64 (64-bit) executable.
>> There seems to be no 32-bit lin
13 matches
Mail list logo