On Mar 19, 2009, at 10:12 AM, D. Richard Hipp wrote:
>
> 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 networ
On Wed, Mar 25, 2009 at 9:55 PM, D. Richard Hipp wrote:
> It is a little more complicated than that, though. The way the built-
> in server for fossil works is that it starts a new child process for
> each incoming request. So somehow the child process that handles the
> request has to notify th
On Mar 25, 2009, at 4:48 PM, Hugo Schmitt wrote:
> What about allowing the client (a setting that would default to off,
> of course) to send a "remote-close" ?
>
Yes. I think that is the right approach.
It is a little more complicated than that, though. The way the built-
in server for fos
What about allowing the client (a setting that would default to off, of
course) to send a "remote-close" ?
On Wed, Mar 25, 2009 at 5:34 PM, D. Richard Hipp wrote:
>
> On Mar 25, 2009, at 3:22 PM, Hugo Schmitt wrote:
>
> > An alternative would be to add an option to the server command, say
> > "
On Mar 25, 2009, at 3:22 PM, Hugo Schmitt wrote:
> An alternative would be to add an option to the server command, say
> "-single", that would automatically stop the server after the first
> pull/push command. So we could just run "fossil server repo.fossil
> &", and then push/pull on the
An alternative would be to add an option to the server command, say
"-single", that would automatically stop the server after the first
pull/push command. So we could just run "fossil server repo.fossil &", and
then push/pull on the same xterm window... simplifying the scripts.
Cheers,
Hugo
On T
On Sat, March 21, 2009 8:02 am, "Michael T. Richter"
wrote:
> On Thu, 2009-03-19 at 19:40 +, Eric wrote:
>
>> I don't think a piece of software has to do
>> everything and I am quite happy to use various tools to build my
>> "everything" around specific software that does a specific task. The
On Thu, 2009-03-19 at 19:40 +, Eric wrote:
> I don't think a piece of software has to do
> everything and I am quite happy to use various tools to build my
> "everything" around specific software that does a specific task. The Unix
> philosophy really.
The Unix "philosophy" has never cut ice
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 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 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 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
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 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 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?
--
Michael T. Richter (GoogleTalk:
ttmrich...@gmail
On Wed, 18 Mar 2009 09:44:49 -0300, you wrote:
> Can I update a repository by copying the db file somehow?
Yes, you can, but copy is a one-way process.
In your case you work either on A or B, never at the same
time. In that case it will work.
1 work on A
2 checkin >> version 1
3 copy A -> pen
Thanks for the fast answer. I'm still experimenting..
Can I update a repository by copying the db file somehow?
(Actually I tried rsyncing the repository file and then "fossil
update", which didn't work)
Cheers,
Hugo
On Tue, Mar 17, 2009 at 5:31 PM, D. Richard Hipp wrote:
>
> On Mar 17, 2009, a
On Mar 17, 2009, at 4:15 PM, Hugo Schmitt wrote:
> Hi again,
>
> One of the reasons I'm interested in fossil is because copying a
> single file to a pendrive is much faster than copying lots of files
> (like other DVCSs), and my workflow for updating my configuration
> between home and work consi
Hi again,
One of the reasons I'm interested in fossil is because copying a
single file to a pendrive is much faster than copying lots of files
(like other DVCSs), and my workflow for updating my configuration
between home and work consists of a pendrive from where I push/pull
from home to work, an
21 matches
Mail list logo
