I'm using 2.4 locally, Chisel says it's using 2.1. If I change a file in a
repository the changes go out properly but adding files to another
repository doesn't work. The push or sync seems to succeed, but the Chisel
web UI does not reflect the change and on clone I get a "manifest checksum
does no
The main GitHub feature that I would like is directions as to how to
download and check out the repository. I like to implement this in
fossil as a footer.
https://thomaslevine.com/scm/langrompiloj/
I believe that someone mentioned this feature in the Fossil-NG Bloat
thread, but I can't find the m
> Your suggestions for useful features found in GitHub but missing from
> Fossil, or for pages in GitHub that work especially well and that you
> would like to see replicated in Fossil, are greatly appreciated.
I think the answers depend on specifics of project workflow.
GitHub is a social platfor
On Sat 25 Nov 2017 9:17 AM, Richard Hipp wrote:
> The SQLite project is mirrored on GitHub (not by me). This mirror
> provides a good opportunity to compare the interfaces of GitHub and
> Fossil using the same underlying data.
>
> https://sqlite.org/srcx/timeline?basic
> https://github.c
On Mon, Nov 27, 2017 at 7:00 AM,
wrote:
>
> Date: Mon, 27 Nov 2017 09:50:29 +
> From: Javier Guerra Giraldez
> Subject: Re: [fossil-users] Trolling GitHub for ideas
>
> the only github think i've really missed when using fossil for
> non-personal projects is the ability to comment on a diff.
I would like yesterdays with a bit of whitespace between commit comments.
Also someone liked the original because the checkin tag was in a
predictable place. If you put the tag last in the extra information it
would be predictably at the right margin.
On 27 November 2017 at 21:01, Richard Hipp
Note that I would retain the rounded corners on Warren’s backgrounds, they make
the visuals “softer”.
On 28 Nov 2017, 10:01 AM +0800, Richard Hipp , wrote:
> On 11/27/17, Steve Landers wrote:
> > Nice work.
> >
> > Have you considered dropping the borders on the commits? They do add
> > definiti
On 11/27/17, Steve Landers wrote:
> Nice work.
>
> Have you considered dropping the borders on the commits? They do add
> definition to the commit, but at the expense of repetition and possibly
> “noise” when the branch isn’t colored
Here are comparison links:
As it was yesterday:
https://ww
Does it stay that size with moderate activity, or does it start growing
significantly? Does the pack format slow it down, or speed it up?
Given that the Git version only has 93% of what the Fossil repo has, I'd
say Fossil is doing quite well.
../Dave
On 27 November 2017 at 16:16, Joerg Sonnenber
Nice work.
Have you considered dropping the borders on the commits? They do add
definition to the commit, but at the expense of repetition and possibly “noise”
when the branch isn’t colored
Screenshot at https://www.dropbox.com/s/o4sa29q8i0dv7r3/timeline.png?dl=0
—Steve
On 28 Nov 2017, 7:02
I use symlinks *very* heavily. Almost exactly 10% of the files in my main
fossil hierarchy are actually symlinks. Fossil not supporting them would be
a huge drawback for me. Good support for symlinks and nested repositories
are 2 of the details I like best about Fossil (in addition to the obvious
f
On 27/11/17 18:02, Warren Young wrote:
> On Nov 27, 2017, at 3:46 PM, Warren Young wrote:
>> On Nov 27, 2017, at 3:41 PM, Richard Hipp wrote:
>>> The big down-side is that less
>>> information is visible on a single screen now, so you have to scroll
>>> more. But that seems to be the trend wit
On Mon, 27 Nov 2017 09:52:19 -0500
Richard Hipp wrote:
> I am in receipt of your patch. I have not evaluated it yet because
> the entire symbolic-link mechanism in Fossil is confused and very
> difficult to manage. It mostly works now, but is brittle. A
> seemingly simple patch like what you s
On Nov 27, 2017, at 3:46 PM, Warren Young wrote:
>
> On Nov 27, 2017, at 3:41 PM, Richard Hipp wrote:
>>
>> The big down-side is that less
>> information is visible on a single screen now, so you have to scroll
>> more. But that seems to be the trend with websites these days….
>
> The design
On Nov 27, 2017, at 3:41 PM, Richard Hipp wrote:
>
> The big down-side is that less
> information is visible on a single screen now, so you have to scroll
> more. But that seems to be the trend with websites these days….
The design ideas I tapped into this were old when desktop publishing was t
On 11/27/17, Warren Young wrote:
>
> table.timelineTable {
> border-collapse: separate;
> }
> td.timelineTableCell {
> vertical-align: top;
> text-align: left;
> padding: 0.75em;
> border: 1px #ccc solid;
> border-radius: 1em;
> }
> span.timelineDetail {
> font-size: 80%;
> text-al
On 27 November 2017 at 14:13, Warren Young wrote:
> On Nov 24, 2017, at 7:35 AM, Richard Hipp wrote:
>>
>> Which is better?
>>
>> A: https://www.fossil-scm.org/a/timeline
>> B: https://www.fossil-scm.org/b/timeline
>
> I prefer A because I don’t like having to dig for details. Hiding details
On Nov 24, 2017, at 7:35 AM, Richard Hipp wrote:
>
> Which is better?
>
> A: https://www.fossil-scm.org/a/timeline
> B: https://www.fossil-scm.org/b/timeline
I prefer A because I don’t like having to dig for details. Hiding details
isn’t the answer to clutter. Drawing the eye to key deta
On Mon, Nov 27, 2017 at 03:28:37PM -0500, Richard Hipp wrote:
> I didn't try any repacking. I merely ran "git clone" then looked at
> the packfile in .git/objects/pack. You would think that the server
> would want to do an aggressive repack before sending the packfile
> across a clone, to save ba
Another issue, taking https://www.fossil-scm.org/fossil/timeline as an
example this time.
- Click `Advanced` to see commits, etc.
- Check `Files` in the toolbar to see files as well
- Page reloads with files... but back in the Basic view
So, advanced should probably be a query parameter here (whe
On Nov 23, 2017, at 5:19 AM, bytevolc...@safe-mail.net wrote:
>
> They want maximum results for minimum effort? That may be normal, but
> it's still whiney.
If “normal” is “whiney”, it ceases to be a useful disparagement unless you
intend to change society. This mailing list is not a good place
On 11/27/17, Joerg Sonnenberger wrote:
> On Mon, Nov 27, 2017 at 02:28:37PM -0500, Richard Hipp wrote:
>> TL;DR: A Git packfile for SQLite is about 52% larger than the
>> equivalent content in a Fossil repository.
>
> Did you run repack with aggresive settings? I.e. with -A -d -f and large
> --de
On Mon, Nov 27, 2017 at 02:28:37PM -0500, Richard Hipp wrote:
> TL;DR: A Git packfile for SQLite is about 52% larger than the
> equivalent content in a Fossil repository.
Did you run repack with aggresive settings? I.e. with -A -d -f and large
--depth and --window-size settings? Especially if the
On 11/27/17, Richard Hipp wrote:
> TL;DR: A Git packfile for SQLite is about 52% larger than the
> equivalent content in a Fossil repository.
It gets worse (for Git):
The Git repo I cloned only contains the master branch - 18336
check-ins out of the 19715 check-ins found in the Fossil repo.
>
TL;DR: A Git packfile for SQLite is about 52% larger than the
equivalent content in a Fossil repository.
I downloaded a copy of the Git packfile from mackyle's mirror of
SQLite on GitHub (https://github.com/mackyle/sqlite). Git uses a
tightly coded binary implementation for packfiles, so I was e
Hi,
I just recently discovered the unversioned files feature and I really like it
for hosting compiled versions like angular 2 and javascript libraries.
I would like to put in a feature request to allow browsers to cache the static
content instead of always downloading the full content over and
On 11/27/17, bytevolc...@safe-mail.net wrote:
> Ping.
I am in receipt of your patch. I have not evaluated it yet because
the entire symbolic-link mechanism in Fossil is confused and very
difficult to manage. It mostly works now, but is brittle. A
seemingly simple patch like what you sent could
Ping.
On Sat, 25 Nov 2017 11:42:29 +
bytevolc...@safe-mail.net wrote:
Index: src/file.c
==
--- src/file.c
+++ src/file.c
@@ -327,24 +327,30 @@
** zFilename is a directory -OR- a symlink that points to a directory.
** Return 0 if
On Mon, Nov 27, 2017 at 1:18 PM, Stephan Beal wrote:
> On Mon, Nov 27, 2017 at 10:50 AM, Javier Guerra Giraldez
> wrote:
>>
>> ideally, on any diff view (a commit, a diff between two versions, a
>> merge preview), i'd like to add comments right there, interleaved with
>> the code. optionally adde
On Mon, Nov 27, 2017 at 10:50 AM, Javier Guerra Giraldez wrote:
> ideally, on any diff view (a commit, a diff between two versions, a
> merge preview), i'd like to add comments right there, interleaved with
> the code. optionally added to a ticket too; so that opening the ticket
> would show all
On 25 November 2017 at 14:17, Richard Hipp wrote:
> Your suggestions for useful features found in GitHub but missing from
> Fossil, or for pages in GitHub that work especially well and that you
> would like to see replicated in Fossil, are greatly appreciated.
the only github think i've really mi
31 matches
Mail list logo
