On Mon, 14 Apr 2014 02:38:14 +0200, Andy Bradford
amb-sendok-1400027895.ngamjincokhalpaij...@bradfords.org wrote:
Thus said j. van den hoff on Sun, 13 Apr 2014 18:37:56 +0200:
only after your and stephan's responses I realize that `default-user'
is _not_ initialized at the time of repo
On Sat, 12 Apr 2014 00:08:49 +0200, Stephan Beal sgb...@googlemail.com
wrote:
On Sat, Apr 12, 2014 at 12:05 AM, j. van den hoff
veedeeh...@googlemail.com
wrote:
A single, shared checkout is your problem. The default-user setting is
set
locally, in the checkout, and does not propagate
On Sun, Apr 13, 2014 at 4:00 PM, j. van den hoff
veedeeh...@googlemail.comwrote:
despite this all being not generally relevant, probably, there remains the
fact that the current behaviour somehow seems inconsistent/buggy from a
user's perspective:
Not for your case. You have multiple users
Thus said Stephan Beal on Sun, 13 Apr 2014 17:54:49 +0200:
question: would this need fixing?
I think at the very least it should be possible to unset a user that was
configured as a default via ``fossil user default user''; perhaps a
``fossil user undefault'' which executes:
DELETE FROM
On Sun, Apr 13, 2014 at 6:12 PM, Andy Bradford amb-fos...@bradfords.orgwrote:
Whether or not the bigger issue of handling default-user as a setting
should be tackled, that's a separate issue in my opinion, though perhaps
the interface should be unified. I started looking into it, but I'm
On Sun, 13 Apr 2014 18:12:05 +0200, Andy Bradford
amb-fos...@bradfords.org wrote:
Thus said Stephan Beal on Sun, 13 Apr 2014 17:54:49 +0200:
question: would this need fixing?
I think at the very least it should be possible to unset a user that was
configured as a default via ``fossil
Thus said j. van den hoff on Sun, 13 Apr 2014 18:37:56 +0200:
only after your and stephan's responses I realize that `default-user'
is _not_ initialized at the time of repo creation/opening but indeed
only via `fossil user default somename'.
It is correct that when you first clone, Fossil
maybe someone can help me understand the problem detailed below. I presume
the question boils down to: 'can I unset the default user?' but
I am not sure. so:
the setup is as follows: a single checkout dir (containing also the fossil
repository itself) on a network disk that is assessed by
On Fri, Apr 11, 2014 at 9:48 PM, j. van den hoff
veedeeh...@googlemail.comwrote:
the setup is as follows: a single checkout dir (containing also the fossil
repository itself) on a network disk that is assessed by several users
under their respective login name (but not simultaneously ...). all
On Fri, Apr 11, 2014 at 10:12 PM, Stephan Beal sgb...@googlemail.comwrote:
A single, shared checkout is your problem. The default-user setting is set
locally, in the checkout, and does not propagate (it even ignores the
--global option, in my tests).
Sorry, hit send too soon. To get out of
On Fri, 11 Apr 2014 22:18:27 +0200, Stephan Beal sgb...@googlemail.com
wrote:
On Fri, Apr 11, 2014 at 10:12 PM, Stephan Beal
sgb...@googlemail.comwrote:
A single, shared checkout is your problem. The default-user setting is
set
locally, in the checkout, and does not propagate (it even
On Fri, Apr 11, 2014 at 4:12 PM, Stephan Beal sgb...@googlemail.com wrote:
Just to have said it: sharing a repo over a network mount is fundamentally
a bad idea, and you will get very little sympathy when things go wrong with
it vis-a-vis a fossil db file.
One of the big advantages of
On Fri, 11 Apr 2014 22:18:27 +0200, Stephan Beal sgb...@googlemail.com
wrote:
On Fri, Apr 11, 2014 at 10:12 PM, Stephan Beal
sgb...@googlemail.comwrote:
A single, shared checkout is your problem. The default-user setting is
set
locally, in the checkout, and does not propagate (it even
13 matches
Mail list logo
