D. Richard Hipp wrote:
>> So... I should put each project in a separate directory otherwise the
>> projects can trample on each other's files. Yes?
>
> On your local machine where you have a check-out, then you can only
> have one check-out per directory. I thought in your previous email
> yo
On Jan 20, 2010, at 5:21 PM, Daniel Carrera wrote:
> D. Richard Hipp wrote:
>> "push" (also "sync" which is a combination of "push" and "pull" done
>> all at once) transfers files from the local myproject.fossil out to
>> the server repository.
>
> So... I should put each project in a separate di
D. Richard Hipp wrote:
> "push" (also "sync" which is a combination of "push" and "pull" done
> all at once) transfers files from the local myproject.fossil out to
> the server repository.
So... I should put each project in a separate directory otherwise the
projects can trample on each other
On Wed, 2010-01-20 at 22:07 +0100, Daniel Carrera wrote:
> 1) "fossil push" -> Does this actually re-create my files on the server
> or does it just update the database file "myproject.fossil" ?
It syncs your local fossil repo (e.g., myproject.fossil) with whatever
external copy of the repo you s
On Jan 20, 2010, at 4:07 PM, Daniel Carrera wrote:
> Hello,
>
> I have some fairly basic questions about using fossil:
>
> 1) "fossil push" -> Does this actually re-create my files on the
> server
> or does it just update the database file "myproject.fossil" ?
"push" (also "sync" which is a co
Hello,
I have some fairly basic questions about using fossil:
1) "fossil push" -> Does this actually re-create my files on the server
or does it just update the database file "myproject.fossil" ?
2) How do I give people passwords so they can commit to the server?
3) Is it reasonable to hold se
6 matches
Mail list logo
