On Wed, Aug 8, 2018, 10:31 AM Petr Man wrote:
I registered in the forum and the password manager didn't save my
> password. I don't see any way of resetting it.
>
I have the same problem. : - (.
Username JayAreJay with the email address I am mailing from here.
Joseph
___
On Sun, Jun 3, 2018, 9:33 PM Richard Hipp wrote:
> On 6/3/18, Richard Hipp wrote:
> >
> > So, if anybody sees any last minute tidying up that we need to do...
>
> For example, on the front page
> (https://fossil-scm.org/index.html/doc/trunk/www/index.wiki), what if
> I add some text to item 8 to
[Response intentionally CC'd to the original poster, on the off chance he's
not already subscribed to the mailing list]
On Mon, Mar 19, 2018 at 7:42 PM, Offray Vladimir Luna Cárdenas <
off...@riseup.net> wrote:
This is just kind of a next semester project, but I would like to start
> exploring t
On Nov 28, 2017 11:08 AM, "Mike Burns" wrote:
As much as I agree, software in general has moved on. You won't get
> Fossil/SQLite running on a Commodore 64 without a lot of work.
> With legacy platforms come legacy software that is either no longer
> supported by the vendor, or is supported just
On Sat, Sep 13, 2014 at 1:37 PM, Ron W wrote:
> I do know how hard handling strings in C is. In the past, I have used
> libawk. I might try to find another lib that provides similar functionality
> or even try to rebuild it (if I can find a copy of the source - not sure I
> still have a copy), b
In
http://www.mail-archive.com/fossil-users@lists.fossil-scm.org/msg14284.html,
Dr. Hipp wrote:
"[...] As part of its role of supporting SQLite, Fossil serves as a test
platform for the latest SQLite alphas. For that reason, I want Fossil 1.28
to have the very latest trunk of SQLite, not the mos
On Thu, Jan 9, 2014 at 8:20 AM, Richard Hipp wrote:
It has been a few months since the last official release of Fossil. I
> wonder if we should consider publishing trunk as the official version 1.28?
>
I realize I am responding to this a little late, but, hey, as a
non-code-contributing blowhar
On Sat, Jan 11, 2014 at 1:24 PM, Jan Nijtmans wrote:
> 2014/1/4 James Turner :
>
> > I won't begin to tell you how to develop fossil but I do want to throw
> > out there that OpenBSD has been providing fossil with
> > --disable-internal-sqlite via it's ports tree and packages fairly
> > successf
On Tue, Jan 7, 2014 at 4:37 AM, Jan Nijtmans wrote:
> 2014/1/7 Joseph R. Justice :
>
> > May I ask why that run-time check cannot or should not be made in the
> > release version of Fossil 1.28, rather than immediately after it is
> tagged
> > such that it will on
On Mon, Jan 6, 2014 at 7:52 AM, Jan Nijtmans wrote:
> 2014/1/4 Richard Hipp :
>
> (3) After SQLite 3.8.3 is released, release fossil 1.28 with
> the EXACT SQLite 3.8.3 amalgamation included.
>
I assume you do not mean here that Fossil v 1.28 should be released
concurrently with SQLite
On Thu, Jan 2, 2014 at 9:52 PM, Nico Williams wrote:
More generally, trying to ensure that a) there's only one copy of
> every library in the distro/OS, b) all version dependencies match up,
> is *super* hard, if not impossible. Eventually there are some very
> commonly used libraries where the
On Sat, Jan 4, 2014 at 11:04 AM, Richard Hipp wrote:
> On Sat, Jan 4, 2014 at 10:59 AM, Joseph R. Justice wrote:
>
>> On Fri, Jan 3, 2014 at 9:28 PM, Richard Hipp wrote:
>>
>
> OK, so I propose the following fix:
>>>
>>
>> [...]
>>
>>
On Fri, Jan 3, 2014 at 9:28 PM, Richard Hipp wrote:
OK, so I propose the following fix:
>
[...]
> (2) Remove the --disable-internal-sqlite option on trunk. Require the
> use of the built-in SQLite only, since SQLite needs to be built with
> non-standard compile-time options to fully meet th
On Fri, Jan 3, 2014 at 2:54 PM, Ron Wilson wrote:
> On Fri, Jan 3, 2014 at 1:50 PM, Joseph R. Justice wrote:
>
> Actually... What I was thinking of here was not anything related to
>> preparation of the software changes or release package, but instead the
>> actual deplo
On Fri, Jan 3, 2014 at 1:22 PM, Ron Wilson wrote:
> On Thu, Jan 2, 2014 at 2:04 PM, Joseph R. Justice wrote:
>
>
>>
>> Further, in the embedded software world at least, I expect it is often
>> difficult or even impossible to update software in the first place
On Fri, Jan 3, 2014 at 12:26 PM, Roy Marples wrote:
> On 03/01/2014 16:41, Lluís Batlle i Rossell wrote:
>
>> On Fri, Jan 03, 2014 at 04:36:26PM +, Roy Marples wrote:
>>
>
> Can fossil create an archive (tarball, zip file, etc) from a given
>>> artifact id WITHOUT using the web interface?
>
On Thu, Jan 2, 2014 at 2:04 PM, Joseph R. Justice wrote:
> [Top-posting considered harmful. *cough*]
>
> On Thu, Jan 2, 2014 at 12:40 PM, B Harder wrote:
> > On 1/2/14, Richard Hipp wrote:
>
> >> The silly requirement of some distributions that *everything* must be
[Top-posting considered harmful. *cough*]
On Thu, Jan 2, 2014 at 12:40 PM, B Harder wrote:
> On 1/2/14, Richard Hipp wrote:
>> The silly requirement of some distributions that *everything* must be a
>> shared library irks me beyond words. I hate having to support
>> --disable-internal-sqlite,
On Mon, Sep 23, 2013 at 7:05 AM, Alaric Snell-Pym
wrote:
> I've written a backup/archival tool based on content-addressible
> storage, and a common question people ask is "So why don't I just put my
> home directory/entire filesystem in git, then?", and I have to raise
> this aspect of the quite
On Wed, Oct 2, 2013 at 10:22 AM, Stephan Beal wrote:
Ignoring the complication of having to parse/grok the content (it's a minor
> complication, granted, but parsing text is always at least a slight
> annoyance), there's another problem: DVCS. i edit the field, then you close
> the ticket in your
On Fri, Aug 2, 2013 at 11:55 AM, Richard Hipp wrote:
> On Fri, Aug 2, 2013 at 11:51 AM, Benedikt Ahrens
> wrote:
>
Hello,
>>
>> I am having trouble with a fossil repository containing many binary files.
>>
>> The fossil version is the one packaged in Debian Wheezy:
>>
>> $ fossil version
>> Th
On Wed, Jul 31, 2013 at 1:05 AM, B Harder wrote:
> I'd suggest: fossil is happy to run wherever it can, and strives for
> portability wherever it can, whenever it makes sense.
>
> Any OS is welcome to modify/redistribute fossil in the terms described in
> the license.
>
Well, sure. Portability i
[Meta: This message is being intentionally sent to _both of_ the
fossil-users and fossil-dev mailing lists, separately, so as to get the
maximum possible feedback and response. I am currently subscribed to both
lists and will see any response you send to either of them. You need not
cross-post yo
[Effing GMail sent this before it was fully responded to. My fault for
writing my response using the GMail web interface instead of composing it
in a text editor like a Real Programmer would have done.]
On Thu, Jul 25, 2013 at 9:17 PM, Joseph R. Justice wrote:
> My apologies for taking so l
My apologies for taking so long to respond myself, I've been a little under
the weather the last couple of days. I appreciate the time you took in
responding to my first message on this thread.
On Tue, Jul 23, 2013 at 4:54 AM, Stephan Beal wrote:
> On Tue, Jul 23, 2013 at 4:30 AM,
On Sun, Jul 21, 2013 at 6:54 AM, Stephan Beal wrote:
Hi, all,
>
> This topic has been tossed around before, but the amount of effort
> involved in its undertaking has always kept us from actually doing it...
>
> To help bootstrap the process of figuring out what Fossil v2 might look
> like i have
On Mon, Jul 22, 2013 at 5:21 AM, Konstantin Khomoutov <
flatw...@users.sourceforge.net> wrote:
> On Sun, 21 Jul 2013 17:01:02 -0700 (PDT) Clark Christensen <
> cdcmi...@yahoo.com> wrote:
>
> > Scripting language: I understand the Tcl roots, and I hope you would
> > consider Javascript as a targe
On Sun, Jul 21, 2013 at 1:12 PM, Eduardo Morras wrote:
> b) Plugins and hooks c modules
>
[...]
> c) source code parser, to find where a function, macro, etc... is
> declared
>
For programs in C and C++ (and presumably eventually other programming
languages), the LLVM Compiler Infrastructure
[This is really more of an administrative or meta issue than it is
something directly applicable to the purpose of fossil-users as I
understand it. However, I am CCing that list in case any subscribers
there have an opinion about this request, since it potentially affects
them. I am currently sub
29 matches
Mail list logo
