On Wed, 22 Nov 2017 19:09:21 -0500
Richard Hipp wrote:
> But making Fossil work as a client for Git is the cornerstone of my
> plan for world domination! :-)
Go for it!
> One important reason that many people use Git is because so much OSS
> is hosted on GitHub and everybody
On Nov 22, 2017, at 9:56 PM, Richard Hipp wrote:
>
> On 11/22/17, Warren Young wrote:
>>
>> 1. Visit https://example.com
>> 2. Click Timeline (and how would my users know to do that?)
>> 3. Click checkin ID.
>> 4. Find and click Tarball link
>> 5. Unpack
On Wed, 22 Nov 2017 21:35:31 -0700
Warren Young wrote:
> [...]
> 1. Visit https://example.com
> 2. Click Timeline (and how would my users know to do that?)
> 3. Click checkin ID.
> 4. Find and click Tarball link
> 5. Unpack the tarball
Well, that's a bit of an exaggeration,
On 11/22/17, Warren Young wrote:
>
> 1. Visit https://example.com
> 2. Click Timeline (and how would my users know to do that?)
> 3. Click checkin ID.
> 4. Find and click Tarball link
> 5. Unpack the tarball
>
> Then they must do all 5 steps again every time there is a new
On Nov 22, 2017, at 7:43 AM, bytevolc...@safe-mail.net wrote:
>
> On Tue, 21 Nov 2017 16:42:56 -0700
> Warren Young wrote:
>
>>> This seems more like a complaint about the user interface.
>>
>> How does that observation get us to a different solution?
>
> Because you
On 22/11/17 19:09, Richard Hipp wrote:
> On 11/22/17, Offray Vladimir Luna Cárdenas wrote:
>> I'm dubious over making Fossil a client for
>> any other main DVCS out there.
> But making Fossil work as a client for Git is the cornerstone of my
> plan for world domination! :-)
On Wed, Nov 22, 2017 at 07:01:31PM -0500, Richard Hipp wrote:
> > (2) Store true differential manifests.
>
> I'm thinking that Fossil-NG will probably do like Git and store
> separate artifacts holding the content of each directory. (Git calls
> these "Tree Objects"). I need to do more
I noticed this curious gem in the test_env web page, which doesn't have
any obvious use case, and I cannot find any mentions of
"test_env?redirect=..." anywhere in the Fossil code base.
Index: src/style.c
==
--- src/style.c
+++
On Wed, 22 Nov 2017 23:43:07 +
Javier Guerra Giraldez wrote:
> i _have_ used fossil running in a very small MIPS system. as
> mentioned, it's really nice to pull versioned stuff like
> configurations, HTML, binary blobs. yes, i used gcc to compile it,
> but what was
On 11/22/17, Offray Vladimir Luna Cárdenas wrote:
> I'm dubious over making Fossil a client for
> any other main DVCS out there.
But making Fossil work as a client for Git is the cornerstone of my
plan for world domination! :-)
One important reason that many people use Git
On 11/22/17, Joerg Sonnenberger wrote:
>
> (1) The need to parse all artifacts on clone. Artificates should be
> strongly typed, i.e. the system should at the very least distinguish
> fully between "content" blobs and "meta data" blobs. Only the latter
> have and should be parsed.
On 22 November 2017 at 23:09, wrote:
> On Wed, 22 Nov 2017 17:30:10 +
> Javier Guerra Giraldez wrote:
>> why not? fossil makes for a neat deployment client! yes, it can also
>> be done with just an http client, but still is a nice option to
On Wed, Nov 22, 2017 at 3:11 PM bch wrote:
>
> On Wed, Nov 22, 2017 at 3:10 PM wrote:
>
>> On Wed, 22 Nov 2017 17:30:10 +
>> Javier Guerra Giraldez wrote:
>> > why not? fossil makes for a neat deployment client! yes,
On Wed, Nov 22, 2017 at 3:10 PM wrote:
> On Wed, 22 Nov 2017 17:30:10 +
> Javier Guerra Giraldez wrote:
> > why not? fossil makes for a neat deployment client! yes, it can also
> > be done with just an http client, but still is a nice option
On Wed, 22 Nov 2017 17:30:10 +
Javier Guerra Giraldez wrote:
> why not? fossil makes for a neat deployment client! yes, it can also
> be done with just an http client, but still is a nice option to have.
Because people do not use compilers on such systems, but rather,
On Mon, Nov 20, 2017 at 01:33:11PM -0700, Warren Young wrote:
> I see a new wiki article:
>
> https://www.fossil-scm.org/index.html/wiki?name=Fossil-NG
There are two central design flaws in Fossil that affect larger
repositories and those are the repos that primarily benefit from
On 2017-11-22 22:43, Thomas wrote:
That was also my understanding in the beginning but it turned out I was
(terribly) wrong. You got to synchronise them manually, and then they're
not pulled automatically either.
I second this approach. Since Fossil already uses "unversioned" for the
current
On 2017-11-22 22:27, Offray Vladimir Luna Cárdenas wrote:
2) Allow me to designate any file in the directory structure as
unversioned. The current unversioning model does not work well for
me. It essentially is equivalent to Dropbox. I am working with
PharoJS which produces Javascript files
Hi Dave,
On 22/11/17 15:27, David Mason wrote:
> Also as a mere fossil user, I would find it useful if fossil could
> respond to a git client and serve files. I use Pharo, which is working
> toward integrated support for git, but I'd much rather trust my bits
> to Fossil. While the Fossil UI is
Also as a mere fossil user, I would find it useful if fossil could respond
to a git client and serve files. I use Pharo, which is working toward
integrated support for git, but I'd much rather trust my bits to Fossil.
While the Fossil UI is nice, I see much less value in using a local Fossil
to
On 22 November 2017 at 14:43, wrote:
> Nobody in their right mind would even consider Fossil (with its
> in-built web server, wiki, and bugtracker) to run on such a system, so
> why bother coding for it?
why not? fossil makes for a neat deployment client! yes, it
Hi,
A minor patch for the enumeration in www/style.wiki.
Included a proposal for a few comments about ANSI C-89.
Best regards,
Johan
Index: www/style.wiki
==
--- www/style.wiki
+++ www/style.wiki
@@ -1,63 +1,89 @@
Coding Style
On Tue, 21 Nov 2017 16:42:56 -0700
Warren Young wrote:
> > This seems more like a complaint about the user interface.
>
> How does that observation get us to a different solution?
Because you then focus on tweaking the UI to make it better, rather
than just stuffing
23 matches
Mail list logo