On Thu, March 19, 2009 2:07 pm, "Michael Richter"
wrote
>
> This is a philosophical point with me: the entire job of software, in my
> opinion, is to do the tedious, repetitive, error-prone stuff in place of
> the
> human, not to make the human do more tedious, repetitive, error-prone
> stuff. Ri
On Thu, March 19, 2009 1:33 pm, "D. Richard Hipp" wrote
>
> Somebody once suggested that I add a new command to fossil that lets
> you enter raw SQL against the repository database file. In other
> words, build the functionality of the "sqlite3" CLI into fossil. I
> rejected the idea at the time
On Thu, March 19, 2009 11:53 am, "D. Richard Hipp" wrote:
>
> It has been suggested that the ability to support multiple local
> checkouts from the same repository is a design flaw in fossil. Hg, it
> seems, supports exactly one local checkout per repository and in fact
> the repository and the l
On Mar 19, 2009, at 8:05 AM, D. Richard Hipp wrote:
>
> On Mar 18, 2009, at 9:25 PM, Michael T. Richter wrote:
>
>> On Tue, 2009-03-17 at 16:31 -0400, D. Richard Hipp wrote:
>>>
>>> The "push" and "pull" commands both require network transport.
>>
>> Is there any chance that this could be enhance
2009/3/19 Kees Nuyt
> Not the simplest script, but not too difficult for the
> target audience, IMHO.
This is a philosophical point with me: the entire job of software, in my
opinion, is to do the tedious, repetitive, error-prone stuff in place of the
human, not to make the human do more tediou
On Thu, 19 Mar 2009 19:53:05 +0800, you wrote:
>2009/3/19 Kees Nuyt
>
>> >> The "push" and "pull" commands both require network transport.
>>
>
>> > Is there any chance that this could be enhanced to go straight
>> > off of a file instead of through a network transport?
>
>> Why would that be an
On Mar 19, 2009, at 9:26 AM, D. Richard Hipp wrote:
>
> On Mar 19, 2009, at 9:17 AM, Rene Zaumseil wrote:
>>
>> 4. drh's tip failed
>> sqlite3 t.fsl 'pragma page_size=16384; vacuum'
>> SQL error: SQL logic error or missing database
>>
>> sqlite3
>> SQLite version 3.2.8
>
> 3.2.8? Wow. That's *r
On Mar 19, 2009, at 9:17 AM, Rene Zaumseil wrote:
>
> 4. drh's tip failed
> sqlite3 t.fsl 'pragma page_size=16384; vacuum'
> SQL error: SQL logic error or missing database
>
> sqlite3
> SQLite version 3.2.8
3.2.8? Wow. That's *really* old. Can you try again with a more
recent version of SQ
Hi,
some additional infos to the test case with file test/t.tgz:
1. Create
fossil new t.fsl
project-id: cc61147ca74309335780e376498e4ee10cdb535b
server-id: 4c123bb92b482882c970d43357ec9bc9e1a46b33
admin-user: rene (initial password is "f6fb86")
2. Init
cd test
fossil open ../t.fsl
fossi
On Mar 18, 2009, at 9:25 PM, Michael T. Richter wrote:
> On Tue, 2009-03-17 at 16:31 -0400, D. Richard Hipp wrote:
>>
>> The "push" and "pull" commands both require network transport.
>
> Is there any chance that this could be enhanced to go straight off
> of a file instead of through a network
2009/3/19 D. Richard Hipp
> It has been suggested that the ability to support multiple local
> checkouts from the same repository is a design flaw in fossil. Hg, it
> seems, supports exactly one local checkout per repository and in fact
> the repository and the local checkout are the same thing.
On Mar 19, 2009, at 7:31 AM, Hugo Schmitt wrote:
> Hello,
>
> Do I ever need to (or "when should I") "fossil close" ?
> Is the myrepo.fossil file updated when I `close' (I mean, should I
> close before cloning or something?)
Nothing in the "myrepo.fossil" file changes when you "close". Close
2009/3/19 Kees Nuyt
> >> The "push" and "pull" commands both require network transport.
>
> > Is there any chance that this could be enhanced to go straight
> > off of a file instead of through a network transport?
>
> Why would that be an advantage?
Count the keystrokes and the commensurat
On Mar 19, 2009, at 6:46 AM, Kees Nuyt wrote:
> On Thu, 19 Mar 2009 10:03:26 +0100, you wrote:
>
>> Hi,
>>
>> I would use a binary (*.tgz) file in my repository. The file is
>> near 20 MB.
>> The first add is immediately. After changing the file, the commit
>> takes
>> nearly half an hour?
>>
Hello,
Do I ever need to (or "when should I") "fossil close" ?
Is the myrepo.fossil file updated when I `close' (I mean, should I close
before cloning or something?)
Tks
-Hugo
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.
FTR, I wanted to rsync the repo because writing a script to synchronize a
bunch of fossil repositories would be a little boring, because one needs to
create the server on one side and push in the other side.
Cheers,
Hugo
On Thu, Mar 19, 2009 at 7:34 AM, Kees Nuyt wrote:
> On Thu, 19 Mar 2009 09
On Thursday 19 March 2009 20:50:20 Dan wrote:
> > step...@jareth:~$ f help up
> > Usage: f update ?VERSION? ?--latest?
>
> Forgive my assumption, but i'm not sure that answer fits the question that
> Mark
> is asking..
Indeed, the answer does presume I already have fossil installed.
> I think t
Forgive my assumption, but i'm not sure that answer fits the question that Mark
is asking..
I believe the question is similar to one I have tried to sort out a few times
(and am just about to tackle again.. so the timing is good)..
The issue is that the download link for a particular set of fil
On Thu, 19 Mar 2009 10:03:26 +0100, you wrote:
>Hi,
>
>I would use a binary (*.tgz) file in my repository. The file is near 20 MB.
>The first add is immediately. After changing the file, the commit takes
>nearly half an hour?
>
>Test case with file test/t.tgz:
> fossil new t.fsl
> cd test
> fos
On Thu, 19 Mar 2009 09:25:04 +0800, you wrote:
>On Tue, 2009-03-17 at 16:31 -0400, D. Richard Hipp wrote:
>
>> The "push" and "pull" commands both require network transport.
>
>
>Is there any chance that this could be enhanced to go straight
>off of a file instead of through a network transport?
On Thu, Mar 19, 2009 at 8:29 AM, Mark Constable wrote:
> Would there be a way I could pull the equiv of trunk or
> HEAD/master without manually going to the site first?
Hi, Mark!
i think what you want is:
step...@jareth:~$ f help up
Usage: f update ?VERSION? ?--latest?
The optional argument is
Hi,
I would use a binary (*.tgz) file in my repository. The file is near 20 MB.
The first add is immediately. After changing the file, the commit takes
nearly half an hour?
Test case with file test/t.tgz:
fossil new t.fsl
cd test
fossil open ../t.fsl
fossil add t.tgz
# change file t.tgz
Hi folks, I've have probably missed this in the docs but
maybe there is a way to do what I want. For most projects
I can automate the build procedure by checking out trunk
or HEAD and I do not have to re-edit the build scripts
for each new version or update.
With fossil it looks like I would have
23 matches
Mail list logo
