Ciao,
On Mon, Dec 29, 2014 at 10:17 AM, Baruch Burstein wrote:
> No. The Fossil repo is completely self contained and does not depend in any
> way on the git repo or even on the git-export file it was created from.
>
I've moved the fossil repository file to a location where I'd like to
keep all
On 02/01/15 14:34, Richard Hipp wrote:
> I'm trying to compile a list of interesting public Fossil repositories. My
> list currently includes:
>
> http://www.fossli-scm.org/fossil/
> http://www.sqlite.org/src/
> http://www.eagle.to/cgi-bin/eagle/timeline
> http://core.tcl.tk/tcl/t
Thus said Kelly Dean on Tue, 06 Jan 2015 21:03:03 +:
> That's horrible. You have to re-download the entire repository if one
> packet is lost at the end?
If you're suggesting that Fossil should treat network errors differently
during cloning and complete with whatever artifacts hav
Andy Bradford wrote:
> If the connection times out
> then I would expect the whole operation to fail and the repository be
> deleted.
That's horrible. You have to re-download the entire repository if one packet is
lost at the end?
> I'm curious what Fossil would do with one of the partial cl
Thus said "Ashwin Hirschi" on Tue, 06 Jan 2015 20:08:12 +0100:
> As an alternative, you could try some predefined entities like ↑
> and ↓ (for up- and down-arrow resp.).
These actually render ``prettier'' for me than the Unicode characters,
perhaps because they are older as you suggest. Could
Apparently some unicode arrow characters (U+2b06, U+2b07, and U+21f3)
are not displaying properly on many peoples systems, though they work
fine on every machine and browser I have at hand. Web-experts: What
am I doing wrong? And what can I use as an alternative?
As an alternative, you coul
I have problem on my Iphone (Safari and Chrome on IOS 8.1):
Currently sorted arrow is ok (up and down) but the white up/down
arrow for other columns show empty square.
On all other browser I use, it's ok..
windows 8.1:
IE 11, Chrome 39, Firefox 34
On Tue, Jan 6, 2015 at 8:45 PM, Ron W wrote:
> On Tue, Jan 6, 2015 at 12:32 PM, Richard Hipp wrote:
>
>> Expanding this question from fossil-dev to fossil-users after more
>> reports of problems.
>>
>> Apparently some unicode arrow characters (U+2b06, U+2b07, and U+21f3)
>> are not displaying pr
On Tue, Jan 6, 2015 at 12:32 PM, Richard Hipp wrote:
> Expanding this question from fossil-dev to fossil-users after more
> reports of problems.
>
> Apparently some unicode arrow characters (U+2b06, U+2b07, and U+21f3)
> are not displaying properly on many peoples systems, though they work
> fine
Expanding this question from fossil-dev to fossil-users after more
reports of problems.
Apparently some unicode arrow characters (U+2b06, U+2b07, and U+21f3)
are not displaying properly on many peoples systems, though they work
fine on every machine and browser I have at hand. Web-experts: What
On Tue, Jan 6, 2015 at 11:50 AM, Stephan Beal wrote:
> On Tue, Jan 6, 2015 at 5:12 PM, Ron W wrote:
>
>> The "sym-" one not having a value. Strange to me that 2 tags would be
>> used (I would have thought only the "branch" tag), but looks like the
>> "sym-" tag could be used to hold a branch des
On 1/6/15, Ron W wrote:
> On Tue, Jan 6, 2015 at 4:04 AM, Stephan Beal wrote:
>
>>
>> agreed. AFAIK, branches currently do not use the VALUE part of the tag.
>> Perhaps such a description could be set there when making a branch, e.g.:
>>
>>
>> fossil commit -b new-branch -d "branch description"
On Tue, Jan 6, 2015 at 5:12 PM, Ron W wrote:
> The "sym-" one not having a value. Strange to me that 2 tags would be used
> (I would have thought only the "branch" tag), but looks like the "sym-" tag
> could be used to hold a branch description.
>
One downside: this precludes modifying the descr
On Tue, Jan 6, 2015 at 4:04 AM, Stephan Beal wrote:
>
> agreed. AFAIK, branches currently do not use the VALUE part of the tag.
> Perhaps such a description could be set there when making a branch, e.g.:
>
>
> fossil commit -b new-branch -d "branch description" -m "commit message"
>
> That would
On Tue, Jan 6, 2015 at 6:41 AM, Matt Welland wrote:
> +1 IMHO this is a good idea. How technically feasible it is I have no idea.
>
agreed. AFAIK, branches currently do not use the VALUE part of the tag.
Perhaps such a description could be set there when making a branch, e.g.:
fossil commit -
Thus said Kelly Dean on Sun, 04 Jan 2015 04:21:55 +:
> Yesterday, the network probably dropped some packets. But it's
> misleading, at least for a new user, for Fossil to report that the
> clone finished when it actually didn't.
I have not been able to reproduce this problem. D
16 matches
Mail list logo
