Re: [fossil-users] Fossil-NG ideas

2017-11-20 Thread Warren Young
On Nov 20, 2017, at 3:12 PM, Offray Vladimir Luna Cárdenas wrote: > > I thought that was the extension > the shallow cloned repository would get if no extension name was specified. If you say $ fossil clone https://fossil-scm.org fossil You get a repository file called

Re: [fossil-users] Fossil-NG ideas

2017-11-20 Thread Warren Young
On Nov 20, 2017, at 1:33 PM, Warren Young wrote: > > There is one more thing Git really gets right compared to Fossil: single-step > clone-and-open. We should be able to do the same: I’ve prototyped this as a simple shell script: #!/bin/sh -e url=$1 shift

Re: [fossil-users] Fossil-NG ideas

2017-11-20 Thread Offray Vladimir Luna Cárdenas
OK. My mistake. I misunderstood the post. Cheers, Offray On 20/11/17 18:04, Warren Young wrote: > On Nov 20, 2017, at 3:41 PM, Offray Vladimir Luna Cárdenas > wrote: >> On 20/11/17 17:22, Warren Young wrote: >>> On Nov 20, 2017, at 3:12 PM, Offray Vladimir Luna Cárdenas

Re: [fossil-users] Fossil-NG ideas

2017-11-20 Thread Offray Vladimir Luna Cárdenas
On 20/11/17 16:45, Carlo Miron wrote: > On Mon, Nov 20, 2017 at 9:33 PM, Warren Young wrote: > > >> There is one more thing Git really gets right compared to Fossil: >> single-step clone-and-open. We should be able to do the same: >> >> $ fossil clone

Re: [fossil-users] Fossil-NG ideas

2017-11-20 Thread Warren Young
On Nov 20, 2017, at 2:55 PM, Offray Vladimir Luna Cárdenas wrote: > > On 20/11/17 16:45, Carlo Miron wrote: >> On Mon, Nov 20, 2017 at 9:33 PM, Warren Young wrote: >> >>> When the FILENAME parameter is not given, it produces a “Fossil” >>> subdirectory

Re: [fossil-users] Fossil-NG ideas

2017-11-20 Thread Offray Vladimir Luna Cárdenas
On 20/11/17 17:01, Warren Young wrote: > On Nov 20, 2017, at 2:55 PM, Offray Vladimir Luna Cárdenas > wrote: >> On 20/11/17 16:45, Carlo Miron wrote: >>> On Mon, Nov 20, 2017 at 9:33 PM, Warren Young wrote: >>> When the FILENAME parameter is not

Re: [fossil-users] Fossil-NG ideas

2017-11-20 Thread Carlo Miron
On Mon, Nov 20, 2017 at 9:33 PM, Warren Young wrote: > There is one more thing Git really gets right compared to Fossil: single-step > clone-and-open. We should be able to do the same: > > $ fossil clone https://fossil-scm.org > > When the FILENAME parameter is not

Re: [fossil-users] Fossil-NG ideas

2017-11-20 Thread Warren Young
On Nov 20, 2017, at 1:33 PM, Warren Young wrote: > > I see a new wiki article: > >https://www.fossil-scm.org/index.html/wiki?name=Fossil-NG Shallow clones bear some thinking, too. Let us posit that “fossil clone” takes a -shallow option with no argument, telling it to

Re: [fossil-users] Fossil-NG ideas

2017-11-20 Thread Warren Young
On Nov 20, 2017, at 3:41 PM, Offray Vladimir Luna Cárdenas wrote: > > On 20/11/17 17:22, Warren Young wrote: >> On Nov 20, 2017, at 3:12 PM, Offray Vladimir Luna Cárdenas >> wrote: >>> I thought that was the extension >>> the shallow cloned repository

Re: [fossil-users] Fossil-NG ideas

2017-11-20 Thread Warren Young
On Nov 20, 2017, at 4:04 PM, Warren Young wrote: > > Git allows you to do this in 2 steps: clone & cd. Fossil currently requires > 5, as I showed up-thread. 4 steps. The fifth step in the post starting this thread is part of a separate thought.

Re: [fossil-users] Fossil-NG ideas

2017-11-20 Thread Offray Vladimir Luna Cárdenas
On 20/11/17 17:22, Warren Young wrote: > On Nov 20, 2017, at 3:12 PM, Offray Vladimir Luna Cárdenas > wrote: >> I thought that was the extension >> the shallow cloned repository would get if no extension name was specified. > If you say > > $ fossil clone

[fossil-users] Fossil-NG Bloat?

2017-11-20 Thread bytevolcano
In light of the new wiki article: https://www.fossil-scm.org/index.html/wiki?name=Fossil-NG I suggest not getting too carried away with adding features after features. Most of the stuff here seems good, but everything under "Support For Multiple VCS Formats" seems unnecessary. Fossil

Re: [fossil-users] Fossil-NG Bloat?

2017-11-20 Thread Warren Young
On Nov 20, 2017, at 4:57 PM, bytevolc...@safe-mail.net wrote: > > Why add more complexity and bloat to the Fossil core? Because interoperability. One of the major arguments against using Fossil is that it’s largely a one-way transition today, which messes up muscle memory for both Fossil

[fossil-users] [PATCH] Move #ifdef guards up

2017-11-20 Thread bytevolcano
One of the #ifdef guards in src/utf8.c can be moved up since the fossil_utf8_to_console() function is only ever called on WIN32 platforms anyway. BTW, many guards are "#if defined(_WIN32)" rather than "#ifdef _WIN32" but I'm not sure what is preferred here. Index: src/utf8.c

[fossil-users] Fossil-NG ideas

2017-11-20 Thread Warren Young
I see a new wiki article: https://www.fossil-scm.org/index.html/wiki?name=Fossil-NG I’m glad to see shallow and narrow clones being planned. The section on narrow clones should specify whether these can take on a life independent of the parent repository. That is, can they be used to