On 6/4/2015 12:44 PM, Andy Goth wrote:
On 6/3/2015 8:27 PM, Andy Goth wrote:
After renaming files on a branch, it seems Fossil will allow you only
one successful merge until it loses track of which files are which.
Here's a sequence showing the problem (version 3ffb6a3e62):
[see
The stock Fossil ticketing system is pretty bare-bones. I’d like to see some
ways others have modified the ticketing system to suit their needs.
To kick this off, here are the customizations I have on the repo in front of me
at the moment:
Choice Drop-Down Customizations
—
I’ve made
On 6/3/2015 8:27 PM, Andy Goth wrote:
After renaming files on a branch, it seems Fossil will allow you only
one successful merge until it loses track of which files are which.
Here's a sequence showing the problem (version 3ffb6a3e62):
[see
Everything went back to normal.
Thanks everyone for your help.
--
Ardie H. Hwang
email: i...@ardiefox.me
mobile: +82-10-I-AM-ARDIE
On Jun 5, 2015, at 00:24, Andy Bradford
amb-sendok-1436023460.odmpbmlkmjnmcmjea...@bradfords.org wrote:
Thus said Ardie H. Hwang on Thu, 04
On 6/4/15, Svyatoslav Mishyn j...@openmailbox.org wrote:
Hello,
What did I do on 2015-06-02 ?
Probably one is computed using local time and the other using UTC.
see:
http://chiselapp.com/user/juef/repository/tclsoldout/reports?view=byweekdaytype=ci
vs.
Hello,
What did I do on 2015-06-02 ?
see:
http://chiselapp.com/user/juef/repository/tclsoldout/reports?view=byweekdaytype=ci
vs.
http://chiselapp.com/user/juef/repository/tclsoldout/timeline?n=50y=civ=0
--
http://www.juef.tk/
___
fossil-users
Thus said Ardie H. Hwang on Thu, 04 Jun 2015 13:57:12 +0900:
I did not issue `fossil push` because I wasn't sure whether the local
repo is in stable state or not, although the error occurred at sync
phase.
Based on the output you provided, Fossil hit an assertion during opening
a
Hello,
one thing that puzzles me every time I do fossil command help is the
presence of question marks for oprtional parameters, as in
% fossil help commit
Usage: fossil commit ?OPTIONS? ?FILE...?
while I would expect it to be like
% fossil help commit
Usage: fossil commit [OPTIONS] [FILE...]
Fossil has Tcl heritage through SQLite, also TH1, so it makes sense that
this convention carry through by habit.
I believe very very old Tcl used square brackets in its documentation to
indicate optional arguments, but it quickly switched to question marks to
avoid ambiguity with script
Don't forget to try 'fossil sync --verily'
Tomek
Date: Wed, 3 Jun 2015 21:45:20 -0700
From: Matt Welland mattrwell...@gmail.com
To: Fossil SCM user's discussion fossil-users@lists.fossil-scm.org
Subject: Re: [fossil-users] Irrecoverable repository inconsistency
between local and
10 matches
Mail list logo
