hi,
some 2 weeks ago I already asked the list about this (and solved the
problem for me) but I would appreciate if one of the developers could
look into this, whether it needs fixing:
recently, a (desirable) change was introduced that after
fossil clone http://userid@server/repo myclone.fossil
the local default user is set to `userid' instead of the local user name,
which is usually the preferred behavior in my view. however, sometimes it
is still desirable to have a different local default user (be it the local
user account name or -- if one does not want to "give away" the local
account name --
the true name, e.g.). in this situation I see the following
behaviour:
after the above clone operation plus
fossil clone http://userid@server/repo myclone.fossil
fossil user new localname
fossil user default localname
all commits appear in the timeline with user "localname" (as they should).
however, the GUI says "logged in as `userid' and tickets and wiki changes
appear in the timeline as coming from
user `userid' (i.e. the user having done the clone).
in order to fix this, one has to give the
's' capability to the new default user `localname' _and also_ to remove
the 's' capability for the `userid'. only then the message changes to
"logged in as {localname}" where `localname' is the defined default user.
the question to the developer(s) would be: is the present behaviour
"natural" from some higher perspective? or is it really an inconsistency
that should/could be fixed? I would think that the "default user" setting
should be respected
automatically not only for checkins but also for wiki/ticket changes after
fossil clone http://userid@server/repo myclone.fossil
fossil user new localname
fossil user default localname
without the need to do, additionally,
fossil user capabilities localname s
fossil user capabilities userid a #or whatever except `s'
the current state of affairs (after the first 3 commands, checkins come
from `localname' but wiki changes come from `userid') is not desirable in
my view.
the necessity to remove `s' from user `userid' is especially easy to trip
over (I did...).
another, secondary, observation:
if one does _not_ provide the 's' for `localname' (but removes `s' from
`userid' the GUI says "logged in as ?" (verbatim)
and the user `?' is listed in the timeline as ticket creator, e.g.. I
understand that their is a need to have a(t least a single?) `s'
user but then this case (trying to remove the `s' from the last user
possessing it) should be caught in my view instead of assigning the
timeline entry to user "?".
j.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
