Hello, (tl;dr = 'branches are nice')
ok, this is probably somewhat obvious but it hit me only quite late. In a previous post I wondered whether people use nested / separate repos or one big repo to host a big project (http://lists.fossil-scm.org:8080/pipermail/fossil-users/2014-January/014922.html). What I really wanted then was to be able to see the 'sequence of edits' only applying to a subset of a big project-tree - e.g. to see all changes between points A and B in time, done in project-subdir 'source/GUI' (and ignore all other changes done elsewhere within that timespan). Related post: http://lists.fossil-scm.org:8080/pipermail/fossil-users/2014-July/017347.html I've been experimenting a bit with nested repos, which work nicely but add complexity, but only just now I realise a branch does exactly what I wanted to do - display an isolated sequence of edits. D'oh! Michai _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
