>>>>> "Donald" == Donald J Bindner <[EMAIL PROTECTED]> writes:
Donald> Even with light use, I had used many of the patterns you
Donald> list above. But it was the command summary in the manual
Donald> with its focus on what gets changed that caused a real
Donald> "lightbulb" moment for me. I feel much more comfortable
Donald> with darcs now, because I can remember precisely what is
Donald> being changed by each of the commands I use.
I'm still not convinced that this purpose wouldn't be better served by
giving the summary table more prominence. But you're willing to do
the work, so since you have David's blessing, I guess I am curious
what other users will say.
Donald> I like what you propose above, but I think those groupings
Donald> work better in the form of short "case studies" of typical
Donald> uses of darcs (Chapter 5 "Best practices"). Perhaps that
Donald> chapter could use a summary section.
Unfortunately that chapter is really too thin to support all of the
commands at this point, and it's really more about forms of project
organization that Darcs enables than about Darcs usage per se. What
really needs to be done with my outline is to turn it into a tutorial,
possibly a chapter in the user guide, but more likely a separate
document since I doubt it fits into the source naturally.
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
