This reads better then previous version and more detail is given, thanks. The very last bit (4.2 - Fossil inability to push/pull single branch) sounds somewhat weak, though. Perhaps it could be strengthened by mentioning bundle command as a way to export a branch, but I also think bundle command should be extended to make it truly useful for scenarios like these.
What needs to be additionally done is: 1. Ensure --standalone option extracts the full artifact, not just the last delta which will make a bundle, well, a standalone repo - unless I'm wrong what standalone is supposed to mean. 2. (Optional) Extend the bundle export command so a new repo can be created with export contents automatically imported into it. For example, this way people can export a single check-in as the root before adding further bundles to it. This is useful because cross-merges between repos could be done this way with --force option. Richard, what do you think? Cheers, Steve --------------- Original Message From: Richard Hipp Sent: Thursday, 17 December 2015 03:16 To: Fossil SCM user's discussion Reply To: Fossil SCM user's discussion Subject: [fossil-users] Rewrite of fossil-v-git.wiki. Was: Fossil mentioned on HN Based on comments on HN and on this mailing list, I have attempted to rewrite the fossil-v-git.wiki document (https://www.fossil-scm.org/fossil/doc/trunk/www/fossil-v-git.wiki) to better summarize the differences between the two products. Your feedback on the rewrite, and especially suggestions for improving it, are welcomed. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
