On Dec 8, 2015, at 12:12 PM, Steve Stefanovich <[email protected]> wrote: > > I don't think bundle --standalone option works.
I suspect it’s more likely the case that transplanting code between unrelated repos doesn’t work. The feature was intended only to allow someone with an anonymous clone of a repo to change their clone, then send a shard of that repo to someone with checkin rights on the repo they cloned from. I’ve failed to successfully use the feature to extract a directory’s worth of files into its own repo. (Why do that, you ask? Because my three largest Fossils were converted from svn, where it’s common to have one big repo with a directory per project at the top level. Fossil works better with a repo-per-project structure, so I’m trying to remediate my converted omnibus repos.) Here’s a test case, using the setup dir in Fossil’s own repo as an example: cd ~/src/fossil/skull # or wherever you have it checked out f bun app ~/tmp/tmp.fossil $(find setup -type f) cd ~/tmp mkdir fossil-setup cd fossil-setup f new ../fossil-setup.fossil f open ../fossil-setup.fossil f bun imp ../tmp.fossil --force --publish Output: Imported content: 57e01e1feb0198de unknown 806b01761d5d4254 unknown The checkout directory is empty, except for a .fslckout file. Repeating the import command has no visible effect, and “f ci” claims nothing has changed. The hex values are the artifact IDs from the Fossil main repo. You can see both the size of the bundle file and the target repo grow by about the size of the two files in Fossil’s setup directory, but no files appear in the Files tab of Fossil UI. _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
