Best practices, even for casual users (Was: Recovering from an "unrecord all")

Hi,

Juliusz Chroboczek a écrit :
> Zachary P. Landau a écrit :
> 
> > [...] it should be stressed in the
> > manual that people should not be working on their 'master'
> > repository.  It is always a good idea to have a repository that you
> > push your changes to. That way when you totally screw up, you only
> > did it on your working branch and not the main one.
> 
> Aye.  My personal working habits are described in
> 
>   http://www.abridgegame.org/pipermail/darcs-users/2004-July/002351.html

A nice read, although it already assumes some basic darcs-related knowledge
(like making sense of "a bunch of darcs repositories"). But it does say
that, using only one repository, one improper command might actually
destroy the work of a few months or years.

The manual may indeed need a few more words about setting up different
repositories, *even for a single-man project*, just to be able to branch,
rollback a few patches, and so on. And be safe.

Here is my way through the manual:
 * Getting started                               [CHECK]
   * Creating your repository                    [CHECK]
   * Making changes                              [CHECK]
   * Making your repository visible to others
     There is no "others" involved in my project. This sections talks