> --rename-master renames master > --rename-trunk renames trunk > We should strive to keep the command line UI sane.
In my opinion, preserving the long-standing default import target branch as "trunk" is reasonable, whether we change the semantics of "--rename-trunk" option or not. The notion of default import target branch dates back to ~2010, back then it was fixed as "trunk". The "main-branch" Fossil setting was introduced ~2011 to allow the Fossil trunk branch to be named otherwise, keeping "trunk" as the default. Yet the "master"=>"trunk" import mapping stayed fixed till ~2016, when the --rename-trunk import option was introduced to relax the mapping Git:"master"=><fossil-branch>, which indeed does have an effect of renaming trunk. Througout, this was backwards compatible and "trunk" has been remaining the default import target branch. Git:"master"=>Fossil:"trunk" name mapping is not arbitrary, as we all understand, so the "magic" indeed has a convenience for users who aim to move git repo over to Fossil. Maybe printing a message would make the "magic" mapping fact more explicit. As for the Git<=>Fossil branch mapping in general, it maybe more explicitly described via something like "--branch-map master=trunk" option, or something to that effect. I'm not sure how thouroughly the Fossil import from Git fast-export format has been tested, or which specific use-cases it covers. I guess, one specific area that needs a closer look is branching and tagging, as these are quite differing between Git and Fossil. especially in the git fast-import context. > The git-fast-import format does not support "lightweight" tags, only > anointed ones. Git fast-export exports the lightweight tags via "reset" command such as (Note: there's not date command): reset refs/tags/<lightweight-tag> from :mark _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
