On 5/1/2017 7:02 AM, Warren Young wrote:
I’ve checked in my new Platform Quirks section.
Thanks!
Oddly, I noticed only after doing the first checkin that it used my local user
name (tangent) as the user name on the remote (i.e. fossil-scm.org) repository.
I was able to fix it for a second clean-up checkin by re-cloning under my new
wyoung user name.
I suspect this is a mistake that every new user of a remote repository
maintained with different user naming style makes. As Richard points
out, the displayed name can be corrected by a tag.
Why did it let me do that? Shouldn’t it either have refused to accept a
checkin from user “tangent” or silently used “wyoung” instead, even though my
local clone was made as user “tangent”?
Fossil has a complicated process for deciding what your name is. I
worked out most of the quirks and documented it once upon a time. I'm
not certain that later changes haven't tweaked it some since. See the
section "Fossil username" in this document:
https://www.fossil-scm.org/index.html/doc/trunk/www/env-opts.md
for what I knew to be true when I wrote it. Of course, if it is no
longer true....
--
Ross Berteig r...@cheshireeng.com
Cheshire Engineering Corp. http://www.CheshireEng.com/
+1 626 303 1602
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev