Richard Hipp <[email protected]> writes: > Yes, this is an exceedingly newbie question. But if you have never worked > with a software configuration management (SCM) system and especially with a > distributed SCM (DSCM) like Fossil, then the work-flow is probably pretty > mysterious to you. More experienced hands (read: most others reading this > list and especially those with check-in privileges to Fossil) need to > figure out some way of better explaining how Fossil (and other DSCMs) work > to people who have never seen the concepts before. This is very hard for > us since the core concepts of DSCM are like second nature - it is like > trying to explain how to walk - we can't explain it; we just do it without > thinking.
If I may suggest, from my own similarly newbie perspective, a good start would be putting something on the lines of your message in this thread, which I found very clear, as the (or at least, at the top of) the documentation page on "Branching, Forking, Merging, and Tagging"[1]. What's there now is interesting--and worth having, I think--but it just doesn't answer the user who looks at the docs thinking "I've gotten to the point in playing with Fossil that I need to branch. How do I do that?" [1] http://www.fossil-scm.org/index.html/doc/trunk/www/branching.wiki _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
