On Sat, Apr 28, 2012 at 09:34, Richard Hipp wrote:
>
> On a server, I often have multiple CGI scripts all pointing to the same
> repository. A similar feature, added at the same time, keeps track of all
> of the possible URLs for accessing a repository. On the main Fossil
> webserver for example
On Mon, Apr 30, 2012 at 8:17 AM, Leo Razoumov wrote:
> On Sat, Apr 28, 2012 at 09:34, Richard Hipp wrote:
> >
> > On a server, I often have multiple CGI scripts all pointing to the same
> > repository. A similar feature, added at the same time, keeps track of
> all
> > of the possible URLs for
On Sun, 29 Apr 2012 18:46:49 -0700, Leo Razoumov
wrote:
On Sun, Apr 29, 2012 at 12:08, Kevin Quick wrote:
This isn't quite as convincing an argument to me: I can see the utility
of a
pull/sync from a read-only repository, but a fossil open implies that
one
will be doing work with the
On Mon, Apr 30, 2012 at 5:31 AM, Richard Hipp wrote:
> On Mon, Apr 30, 2012 at 8:17 AM, Leo Razoumov wrote:
>
>> On Sat, Apr 28, 2012 at 09:34, Richard Hipp wrote:
>>
>
[snip]
> I think this means that every time one accesses a repository via
>> cg-bin the repository updates the "baseurl:...
The discussion on keeping the location of checkouts in the repo deb
brought up an interesting thought.
Observing the usage in our teams it is apparent that the distributed nature
of fossil is more of a burden than a benefit 90% of the time but that
remaining 10% of the time we very much appreciat
On Mon, Apr 30, 2012 at 11:13 AM, Matt Welland wrote:
> The discussion on keeping the location of checkouts in the repo deb
> brought up an interesting thought.
>
> Observing the usage in our teams it is apparent that the distributed
> nature of fossil is more of a burden than a benefit 90% of th
Hi,
How can I unset the default user?
I cannot see an option under fossil unset ...?
Users that forget to:
fossil commit -U myusername_notdefault
have their changes assigned to the default and wrong user.
On Mon, Apr 30, 2012 at 11:29 AM, Richard Hipp wrote:
>
>
> On Mon, Apr 30, 2012 at 11:13
On Mon, Apr 30, 2012 at 12:19 PM, wrote:
> Hi,
> How can I unset the default user?
> I cannot see an option under fossil unset ...?
>
Looks like you have to manually change the database. Run "fossil sql" then
type: "DELETE FROM config WHERE name='default-user';"
>
> Users that forget to:
> f
On Mon, Apr 30, 2012 at 09:45, Kevin Quick wrote:
> On Sun, 29 Apr 2012 18:46:49 -0700, Leo Razoumov wrote:
>> And at least in UNIX you really
>> do not want making your repository writable by several people.
>
> Huh? Bob works on stuff and commits it. After Bob commits it, Alice should
> be ab
On Mon, Apr 30, 2012 at 7:25 PM, Leo Razoumov wrote:
> others (chmod 0644 repo.fossil). In the case of CGI the owner is
> whatever your http server likes (www-data on Ubuntu).
Tip: many CGI environments run user CGIs as that user. If you are lucky
enough to have such a service provider, chmod 0
On Mon, Apr 30, 2012 at 13:43, Stephan Beal wrote:
> On Mon, Apr 30, 2012 at 7:25 PM, Leo Razoumov wrote:
>>
>> others (chmod 0644 repo.fossil). In the case of CGI the owner is
>> whatever your http server likes (www-data on Ubuntu).
>
>
> Tip: many CGI environments run user CGIs as that user. If
Before trying your sql, I opened my repo with SQLiteExpert and found
no entry in table config:name = 'default-user'?
Is there a hidden location or is the default-user actually NOT set?
Really confused since I want #3 below to happen BEFORE #2 :(
User Name is determined from the following rules, in
On Mon, Apr 30, 2012 at 2:01 PM, wrote:
> Before trying your sql, I opened my repo with SQLiteExpert and found
> no entry in table config:name = 'default-user'?
> Is there a hidden location or is the default-user actually NOT set?
>
Check the VVAR table in _FOSSIL_. It is probably set there.
On Mon, Apr 30, 2012 at 8:01 PM, wrote:
> Really confused since I want #3 below to happen BEFORE #2 :(
> User Name is determined from the following rules, in order:
> 1. The value of the --user or -U command-line option.
> 2. A username set using the "fossil user default" command
> 3. The value o
On Mon, Apr 30, 2012 at 08:31, Richard Hipp wrote:
> On Mon, Apr 30, 2012 at 8:17 AM, Leo Razoumov wrote:
>>
>> I think this means that every time one accesses a repository via
>> cg-bin the repository updates the "baseurl:..." entry. This would make
>> rsync based replication/backup scripts go n
On Mon, Apr 30, 2012 at 2:16 PM, Leo Razoumov wrote:
> On Mon, Apr 30, 2012 at 08:31, Richard Hipp wrote:
> > On Mon, Apr 30, 2012 at 8:17 AM, Leo Razoumov
> wrote:
> >>
> >> I think this means that every time one accesses a repository via
> >> cg-bin the repository updates the "baseurl:..." en
We've had several folks get very confused by the accidental creation of
forks. The conversation goes something like this:
DeveloperA: "Go ahead and update, I've checked in change xyz"
DeveloperB: "Ok" (pause) "I don't see it are you sure you checked it in ...
"
and fifteen minutes later I get a c
17 matches
Mail list logo
