Fossil SCM
choice of default user for fresh clone
c7e41cad6279197…
· opened 12 years, 5 months ago
- Type
- Feature_Request
- Priority
- —
- Severity
- Minor
- Resolution
- Fixed
- Subsystem
- —
- Created
- Oct. 17, 2013 3:48 p.m.
after a clone operation which explicitely specifies a user, e.g.,
fossil clone http://[email protected]/path_to_project project.fossil
it still is the user name of the local account doing the clone that is defining the initial "default user". it would seem wiser to automatically create and set the default user to "kirk" in this example (i.e. to the user name specified during the clone, if any (and only fall back to local user name if this is not the case). I presume the "kirk" user should also get "v" capability (in order to be able to actually checkin). otherwise, if I forget to do
fossil user add kirk fossil user default kirk
(and at least `fossil user capabilities kirk v', I believe) the next checkin will unintentionally use my local user name (which I even might want not be broadcasted and ending up in the timeline display of the server repo).
Comments (2)
after a clone operation which explicitely specifies a user, e.g.,
fossil clone http://[email protected]/path_to_project project.fossil
it still is the user name of the local account doing the clone that is defining the initial "default user". it would seem wiser to automatically create and set the default user to "kirk" in this example (i.e. to the user name specified during the clone, if any (and only fall back to local user name if this is not the case). I presume the "kirk" user should also get "v" capability (in order to be able to actually checkin). otherwise, if I forget to do
fossil user add kirk fossil user default kirk
(and at least `fossil user capabilities kirk v', I believe) the next checkin will unintentionally use my local user name (which I even might want not be broadcasted and ending up in the timeline display of the server repo).
Fixed in [64aa75260f], confirmed by OP.