On Mon, Nov 21, 2011 at 2:13 AM, Richard Hipp wrote:
>
>
> On Sun, Nov 20, 2011 at 7:56 PM, Chris Peachment wrote:
>
>> ...
>
> but I can not find a command to provide the project-name value to
>> be stored in the config table.
>>
>
> There isn't one - or at least not a simple one. I always con
Thank you for providing the key concept to use the configuration
import command with a generated configuration file.
I had been attempting to alter the repository configuration one
field at a time using the command line fossil operations but this
is a much simpler approach.
I have the scripting d
On 21 Nov 2011, at 01:13, Richard Hipp wrote:
>
> On Sun, Nov 20, 2011 at 7:56 PM, Chris Peachment wrote:
>> I'm using fossil version 1.20 on Linux for both server and client
>> computers.
>>
>> I want to use fossil command line instructions to initialise an
>> empty repository. I use:
>>
>>
As indicated in my statements below your insert, I have tried
using the raw SQL approach. The insert statement shown there
was derived from looking at the config table of a dummy
repository.
The motivation for using command line entries is that I'm doing
it for 25 repositories at the moment and an
On Sun, Nov 20, 2011 at 7:56 PM, Chris Peachment wrote:
> I'm using fossil version 1.20 on Linux for both server and client
> computers.
>
> I want to use fossil command line instructions to initialise an
> empty repository. I use:
>
> fossil new test.fossil
>
> but I can not find a command to pr
I'm using fossil version 1.20 on Linux for both server and client
computers.
I want to use fossil command line instructions to initialise an
empty repository. I use:
fossil new test.fossil
but I can not find a command to provide the project-name value to
be stored in the config table.
The follo
6 matches
Mail list logo
