Re: [fossil-users] Trolling GitHub for ideas
On 30 November 2017 at 02:21, Jungle Boogiewrote: > It's possible to highlight lines (or multiple lines) in fossil, but you > need to manually edit the URL: > https://www.fossil-scm.org/index.html/artifact?ln=45-52=24bd6b806af1782c this is great, wish i knew that before! -- Javier ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Trolling GitHub for ideas
On 25 November 2017 at 14:17, Richard Hippwrote: > 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 missed when using fossil for non-personal projects is the ability to comment on a diff. I have two different usecases for that: the first and most obvious is to open a commit, check the diff (from the previous version) and add comments about the changes actually done. if it goes on the right direction, missing stuff, etc. depending on context, what i tend to do is either edit the commiit's comment, or file a ticket with a link to the commit. the latter is the most "correct" way, but it's harder to keep in context. and neither allows me to reference a specific point in the code. the second case is when a branch is nearing completion and becomes a candidate for merging. then, i review the diff and should file a ticket. but it's hard to reference the diff itself. (yes, copy/paste the url works but it's tedious and error prone). again, no way to link a comment with a specific line. is there a way to see what a merge would do in diff style? that alone replaces most of the functionality of Pull Requests. 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 related comments, each with a short view of the code and a link to the full context. -- Javier ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil-NG Bloat?
On 22 November 2017 at 23:09, <bytevolc...@safe-mail.net> wrote: > On Wed, 22 Nov 2017 17:30:10 + > Javier Guerra Giraldez <jav...@guerrag.com> 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, they > use other systems that can compile for the target system. 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 small two years ago now might be in the same boat as that. >> but i haven't seen any reason to promote a language switch. nice as >> they are, C11 features make only easier development; not better code, >> much less any performance improvement or any user-visible advantage. > > I am not suggesting a language switch (C11 is still C) and I'm also > not suggesting just use C11 for the sake of it. Rather, I am suggesing > using modern C features to clean up the code and allow the compiler to > optimise it better. For example, postponed variable declarations, > inline functions, stdint.h definitions, etc. This isn't even C11 stuff, > it's all basic C99 functionality which has been around for 18 years. all those features have zero impact on the generated machine code. > What sort of weird targets does SQLite run on which require the use of > a very old (or broken) compiler that can't handle any C99 features? MS Visual Studio -- Javier ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Fossil-NG Bloat?
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 can also be done with just an http client, but still is a nice option to have. but i haven't seen any reason to promote a language switch. nice as they are, C11 features make only easier development; not better code, much less any performance improvement or any user-visible advantage. SQLite _is_ used on lots of weird targets, and there's much shared code, and most importantly, shared code style. introducing an artificial split between them doesn't seem a good use of developer time. -- Javier ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Content-Security-Policy Was: Fossil README symlink
On 18 October 2017 at 15:32, Stephan Bealwrote: > LOL. Turing and his silly Test - that's why we can't have nice things. nitpicking: it's not about the test, but about the completeness (AKA the halting problem) -- Javier ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Shameless self-promotion
On 15 September 2017 at 15:26, Olivier R.wrote: > I also wonder what’s the best way to include a one-time patch without giving > rights to the repository. one word: bundles -- Javier ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] How to transfer/move/upload local repository to chiselapp.com
On 15 May 2017 at 21:02, The Tickwrote: > That was exactly what I was doing -- after clicking 'Create Repository' my > focus was on the form and I was totally oblivious to the additional options > that had appeared. just for the record, in the "create repository" form, there's an "Override project code" option, with a short explanation "(Optional, but may be needed if pushing an already created repo to Chisel.)" that allows that option to work. just copy there the existing project's code and it will accept your push. -- Javier ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Longest gap between check-ins
On 20 February 2017 at 15:39, Richard Hippwrote: > 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 an IoT (aka DDOS source) device! :-) -- Javier ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
Re: [fossil-users] Using Fossil SCM with Master Repositories held on a Flash Drive ?
On 20 January 2017 at 13:08, Richard Hippwrote: > But have you considered doing it using your network? Are all of your > machines at least intermittently connected to a network? > > So on some central machine that is usually accessible to the others, > put all of your master repositories in a folder named (for example) > C:\fossils. chiselapp.com offers private repositories. -- Javier ___ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users