Hi all,
I've recently written a simple wrapper for Fossil with the goal of
providing an improved CLI experience and thought others might find it
useful.
The script is written in Tcl/Expect and provides the following features:
* Command aliasing
* Output filtering
* A number of
Small feature request (or RfD): It would be neat if adjacent Wiki changes
were grouped so that instead of seeing a sequence like:
timestamp [artifact id] Changes to wiki page [Foo] (user: marc)
timestamp [artifact id] Changes to wiki page [Foo] (user: marc)
timestamp [artifact id] Changes
It seems that commit [f76d912f1d] (which modified the base SQL used in
timeline queries) has introduced a bug into trunk: nothing is returned when
event types are specified as switches to `timeline'.
Demonstration: here's the timeline for wiki pages in the main Fossil repo
output by build
On Sun, Jan 20, 2013 at 4:29 PM, Richard Hipp d...@sqlite.org wrote:
On Sun, Jan 20, 2013 at 1:35 AM, Marc Simpson m...@0branch.com wrote:
It seems that commit [f76d912f1d] (which modified the base SQL used in
timeline queries) has introduced a bug into trunk: nothing is returned when
The following output is a tad puzzling,
--8--
$ fossil pull
Pull from http://www.fossil-scm.org/
Round-trips: 1 Artifacts sent: 0 received: 68
Pull finished with 332 bytes sent, 4436 bytes received
$ fossil sync
Sync with
Hi all,
I've just encountered a scenario in which file mode information is lost
following a merge. This involves (a) adding an executable file, (b)
renaming it in a branch, then (c) merging back into trunk.
To replicate,
$ repo=tmp
$ fossil new $repo.fsl; mkdir $repo; cd $repo
$
It seems that unshunning is currently broken. To reproduce:
(1) Create a test repository,
$ fsl version
This is fossil version 1.26 [a60b008f1a] 2013-07-26 15:46:01 UTC
$ fsl new tmp.fsl
$ mkdir tmp; cd tmp
$ fsl open ../tmp.fsl
$ touch a
$ fsl add a; fsl commit -m a a
$ fsl ui
On Mon, Jul 29, 2013 at 3:03 PM, Warren Young war...@etr-usa.com wrote:
On 7/28/2013 13:47, Marc Simpson wrote:
Output: Cross-site request forgery attempt.
That's a browser-specific feature, not something Fossil does. It may be
that Fossil could work differently to avoid triggering
On Wed, Aug 21, 2013 at 3:36 PM, Stephan Beal sgb...@googlemail.com wrote:
DVCSs cannot, by their very nature, portably support sequential numbers.
This topic has been beaten to death by brains much larger than mine.
Joerg's original proposal (in a previous thread) was to support
_local_
The latest changes to TH1 in trunk (0e6862046d) break 'fossil ui' on my machine:
- ERROR: no such command: if at the top of the page, indicating the
source of the problem;
- Consequently, broken stylesheets etc.
Might be worth moving 0e6862046d to a new branch and fixing there.
Do you want to grant them permission to edit all tickets, or just
those submitted?
If the former, take a look at the 'w' privilege on /setup_ulist.
On Fri, Mar 14, 2014 at 4:51 PM, j. van den hoff
veedeeh...@googlemail.com wrote:
stupid question maybe: it seems that ticket editing is restricted
Since [5d536c51b6]:
./src/http.c:152:40: error: non-void function 'save_httpauth_prompt'
should return a value [-Wreturn-type]
if( (g.urlFlags URL_REMEMBER)==0 ) return;
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
I'd rather autosync remained a toggle (indicating whether work is
local or not). A separate setting for number of retries seems
reasonable.
On Thu, May 29, 2014 at 3:56 PM, Stephan Beal sgb...@googlemail.com wrote:
On Thu, May 29, 2014 at 4:53 PM, Richard Hipp d...@sqlite.org wrote:
On Thu,
On Wed, Sep 3, 2014 at 9:49 AM, Gour g...@atmarama.net wrote:
(5) Create a new command and perhaps a new web page that will publish
(make public) a private branch or check-in. I don't yet know what
this command is called. (publish? Other suggestions?)
'publish' sounds good to me.
Other
On Fri, Oct 10, 2014 at 9:08 AM, Stephan Beal sgb...@googlemail.com wrote:
On Fri, Oct 10, 2014 at 10:01 AM, Ramon Ribó ram...@compassis.com wrote:
If autosync is activated, of course it should do it. In fact, I see it
as an error not doing it. Does not 'autosync' means: do all the pushes
and
This may be of interest to some here, especially in light of previous
SHA-1 related discussions on list:
https://security.googleblog.com/2017/02/announcing-first-sha1-collision.html
/M
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
On Thu, Dec 1, 2016 at 8:46 AM, Richard Hipp wrote:
> There is now a "fossil all ui" command that pops up a list of all
> known repositories. It appears to work on both unix and windows.
Am I correct in thinking that repositories must confirm to the .fossil
naming convention?
On Mon, Mar 27, 2017 at 10:40 AM, Christophe Gouiran
wrote:
>
> please find an attached patch which implements a new "current" subcommand for
> "branch".
> This is now the default subcommand if one executes "fossil branch" without
> any subcommand.
While the addition of
On Wed, Mar 29, 2017 at 7:54 PM, Andy Bradford wrote:
> Maybe one day nvi will have UTF-8 support, but I'm not counting on it
> any time soon. :-)
You may want to check out https://github.com/lichray/nvi2.
___
fossil-users
On Tue, Apr 4, 2017 at 7:01 AM, Warren Young wrote:
>
>
> > $ sudo mv ~/Downloads/fossil /usr/local/bin/fossil
> > $ fossil up
> > dyld: Library not loaded: /usr/local/opt/openssl/lib/libssl.1.0.0.dylib
>
> Looks like you should build from source, or get your binary from
(when a reload
is required).
/M
On Sun, Nov 26, 2017 at 1:27 AM, j. van den hoff <veedeeh...@gmail.com> wrote:
> On Sat, 25 Nov 2017 23:51:23 +0100, Marc Simpson <m...@0branch.com> wrote:
>
>> One other (potential) problem: without the hash prefix, descriptions
>>
One other (potential) problem: without the hash prefix, descriptions
run together.
Example: http://www.sqlite.org/src/timeline, 2017-11-24. The graph
nodes are flushed to the left, so descriptions appear as:
Add the "^" syntax from fts3/4 to fts5. ...
Enhance the configure script to detect
Re: CSS issues: I think the default skin would be a bit more readable
with 1 or 2 pixels of space between these newly added commit
bubbles/boxes.
(Adjacency currently yields a doubly thick shared line.)
On Thu, Nov 30, 2017 at 7:16 AM, jungle Boogie wrote:
> On 30
23 matches
Mail list logo