On 3/11/2015 12:49 AM, Graeme Pietersz wrote:
> On 11/03/15 00:45, Ron W wrote:
>> I'm thinking he wants 2 sets of default settings: The existing one
>> (which he perceives as being open source oriented) and another set
>> that are more appropriate for use by software teams within a
>> "corporate e
On 3/11/2015 12:15 AM, jungle Boogie wrote:
> I created a test repo with a few commits:
>
> The commit of the 100 MB files took about 300 seconds but this ran on
> a single core 512MB-1gig RAM machine.
>
> I know this is unscientific but it seems fossil handled the large
> pretty commits well. If
On 11/03/15 00:45, Ron W wrote:
I'm thinking he wants 2 sets of default settings: The existing one
(which he perceives as being open source oriented) and another set
that are more appropriate for use by software teams within a
"corporate environment".
It would be nice to have, and not ju
Hi Joerg,
On 10 March 2015 at 17:03, Joerg Sonnenberger wrote:
> On Tue, Mar 10, 2015 at 06:14:10PM -0400, Ron W wrote:
>> On Tue, Mar 10, 2015 at 5:54 PM, Joerg Sonnenberger > > wrote:
>> >
>> > Unless "large files" means "larger than 2GB", I don't believe there is
>> > one. I haven't run into a
The new search functionality is awesome and quick - thanks, drh. It is a huge
step forward to make Fossil usable for non-programmers, i.e. GUI-only users
(managers, testers, documentation writers).
It's not quite there yet, IMHO. drh - and other valued contributors - what do
you think about fi
On Tue, Mar 10, 2015 at 06:14:10PM -0400, Ron W wrote:
> On Tue, Mar 10, 2015 at 5:54 PM, Joerg Sonnenberger > wrote:
> >
> > Unless "large files" means "larger than 2GB", I don't believe there is
> > one. I haven't run into a case where I wanted to use version control
> > systems for handling suc
On Tue, Mar 10, 2015 at 5:54 PM, Joerg Sonnenberger wrote:
>
> Unless "large files" means "larger than 2GB", I don't believe there is
> one. I haven't run into a case where I wanted to use version control
> systems for handling such files yet...
I posted a comment and he replied that his commits
On Tue, Mar 10, 2015 at 04:52:05PM -0400, Ron W wrote:
> I suspect the main reason was the problem with large files, whatever his
> threshold for large is. Not a limit I've run into, yet.
Unless "large files" means "larger than 2GB", I don't believe there is
one. I haven't run into a case where I
On Tue, Mar 10, 2015 at 4:37 PM, jungle Boogie
wrote:
>
> On 10 March 2015 at 12:15, Ron W wrote:
> > Many issue tracking systems have a GUI, "point and click" query
> > builder/editor. So, SQL use can be mostly avoided.
> >
> > Creating such a query builder (probably in Javascript) for Fossil mi
On Tue, Mar 10, 2015 at 4:37 PM, jungle Boogie
wrote:
>
> On 10 March 2015 at 12:15, Ron W wrote:
> > Seems to me that he doesn't realize that Fossil separates the repository
> > from the "working copy". He's expecting "fossil clone" to work like Git
> or
> > Hg where the working copy is automati
Thus said Richard Hipp on Mon, 09 Mar 2015 23:52:16 -0400:
> Oh, it does. Try a graph with "n=all" and you'll see. When you start
> to get a lot of rails, and the graph gets all scrunched together, then
> (2) is clearly better. The question is should we go with (2) always,
> or use (1) for gra
Hi Ron,
On 10 March 2015 at 12:15, Ron W wrote:
> On Tue, Mar 10, 2015 at 1:58 PM, jungle Boogie
> wrote:
>>
>> BTW, referring link was this:
>> http://www.omiyagames.com/farewell-fossil-version-control/
>>
>> Author's main complaints about Fossil were:
>
> ...
>>
>> -Author thought you had to ru
Although both are good, my vote is for nomo=0 (choice 1) as being the one
that 'goes to 11' :)
-Original Message-
On Mon, Mar 09, 2015 at 11:06:59PM -0400, Richard Hipp wrote:
Which timeline graph do you prefer:
(1) https://www.fossil-scm.org/fossil/timeline?y=ci&nomo=0
(2) https://ww
On Tue, Mar 10, 2015 at 1:58 PM, jungle Boogie
wrote:
> BTW, referring link was this:
> http://www.omiyagames.com/farewell-fossil-version-control/
>
> Author's main complaints about Fossil were:
>
...
> -Author thought you had to run sql each time to list tickets.
>
Many issue tracking systems
Wow -- is that ever subtle... now that I see it, I think I like nomo=1
-bch
On 3/10/15, Martin S. Weber wrote:
> On 2015-03-09 21:42:51, Andy Bradford wrote:
>> Thus said Richard Hipp on Mon, 09 Mar 2015 23:06:59 -0400:
>>
>> > Which timeline graph do you prefer:
>> >
>> > (1) https://www.fossi
Hi Andrew,
On 10 March 2015 at 11:33, Andrew Moore wrote:
> Hello!
>
> Sorry the font was to small for you (I contributed the skin), that change
> looks good.
Thanks for the contributions!
>
> Do you mind sharing which browser and OS you are using? I would like to try
> to reproduce the issue.
Hello!
Sorry the font was to small for you (I contributed the skin), that change
looks good.
Do you mind sharing which browser and OS you are using? I would like to
try to reproduce the issue.
As far as fonts go, all font sizes should be relative (using the "rem"
value suffix) to the font size d
On 10 March 2015 at 09:55, jungle Boogie wrote:
> Not that I'm even remotely interested in project, but I thought I'd
> share it because it's so similar to Fossil:
> http://veracity-scm.com/
BTW, referring link was this:
http://www.omiyagames.com/farewell-fossil-version-control/
Author's main c
On Tue, Mar 10, 2015 at 4:47 AM, Steven Harford
wrote:
> I prefer (2). It's more concise and looks great in each of the examples
> you provided. Therefore, I'm not sure it's worth maintaining both display
> styles in the source code.
>
Also agree
___
f
On 3/10/2015 3:47 AM, Steven Harford wrote:
> I prefer (2). It's more concise and looks great in each of the examples
> you provided. Therefore, I'm not sure it's worth maintaining both
> display styles in the source code.
Agree.
--
Andy Goth |
signature.asc
Description: OpenPGP digital sign
2015-03-09 23:06 GMT+01:00 Tontyna :
> Hurray and thank you!
>
> Will `addremove` become `addforget`? (Sorry, couldn't resist nitpicking.)
It should be 'addforgetrename', with the added functionality that
renames are detected too ;-)
Regards,
Jan Nijtmans
_
I prefer (2). It's more concise and looks great in each of the examples
you provided. Therefore, I'm not sure it's worth maintaining both
display styles in the source code.
Warm regards,
Steven
On Mon, Mar 09, 2015 at 11:06:59PM -0400, Richard Hipp wrote:
Which timeline graph do you prefer:
22 matches
Mail list logo
