> commit refs/heads/shunning_error > mark :56263 > committer drh <drh> 1257360677 +0000 > data 24 > * from :56264
This is a curious case: looks like the branch:"shunning_error" starts off a tag (https://www.sqlite.org/src/info/f228c7ca0682c370f8c43) That is its parent is a commit edit/amend event, unlike normal branches which are children of other commits. The from mark (56264) seems to be the "next-value" of the mark sequence, which export.c::mark_name_from_rid() returns in case when look-up for the checkin id (parent in this case) finds nothing. Obviously from-mark is expected to be previously declared. This case seems like a detached/free-standing branch. From Git fast-import format description: "Omitting the from command in the first commit of a new branch will cause fast-import to create that commit with no ancestor. This tends to be desired only for the initial commit of a project. If the frontend creates all files from scratch when making a new branch, a merge command may be used instead of from to start the commit with an empty tree." Apparently this is a result of some unusual fix-up (https://www.sqlite.org/src/info/eb7a544fe49d1626) I thought with Fossil the repository tree stems from the root/initial commit and technically all branches have a common ancestor commit (root), so there're no detached branches. _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
