I don't think bundle --standalone option works. See my case here: http://www.mail-archive.com/fossil-users%40lists.fossil-scm.org/msg21596.html
S. From: to...@acm.org Sent: Tuesday, 8 December 2015 20:11 To: Fossil SCM user's discussion Reply To: Fossil SCM user's discussion Subject: [fossil-users] BUNDLE problems/questions - resent to the correct list this time :) 1. I’m trying to create a new repo by taking a branch from an existing one. So, I thought the easier way would be the new ‘bundle’ feature. I tried this batch file (Win7): ----------------- f new xxx.fossil --date-override 2014-01-01 f o xxx.fossil f bun export xxx --standalone --branch %1 –R original.fossil f bun import xxx --publish --force ----------------- where %1 is replaced by the name of the branch I want to extract. The --date-override is only there to place the initial empty commit before the imported content. But, it makes no difference if I use it or not. The problem: For some branch trying to “FOSSIL UPDATE branch” (from the initial empty trunk) works fine, and all the files are checked out. Doing the exact same thing for a different branch, however, gives me: content missing for ... each file ... missing content, unable to update If I use the UI I can see the file contents just fine. So, the files are there but, for whatever reason, inaccessible. What can be the cause of this? Why does the above sequence of commands work for one branch but not another (from the same repo)? 2. Can I make the imported bundle end up in trunk without manually shunning the initial empty commit, and making the first node of the imported bundle branch the beginning of a new branch named ‘trunk’? Thanks.
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
