Fossil SCM
import does not support specifying a default user
d1ea61eecf935d6…
· opened 15 years ago
- Type
- Feature_Request
- Priority
- —
- Severity
- Minor
- Resolution
- Not_A_Bug
- Subsystem
- —
- Created
- March 23, 2011 2:36 p.m.
fossil import does not understand "-A USERNAME" command-line option anywhere in its arguments list when it creates a new repository from the data being imported.
While it seems like just a minor inconvenience (it is), this also poses a problem for Windows users who happen to use Cyrillic login names as fossil does not seem to handle this case well and creates the default repo user whose username contains gibberish. As there's no way to expunge a once created user from the repo completely, there should be a way to specify such a user correctly at the repository creation phase.
Hence I think it would be great if in the "create new repo" mode fossil import would behave more like fossil new in this regard.
Comments (1)
I think I got a workaround on Unix, no idea about windoze:
$ export USER=my_special_username $ cat git-export | fossil import new-repo.fossil
I prefer to do this on a brand new (temporary) shell session. I have no idea about how different software will behave when USER env var has a value different than the user's login name.