[darcs-users] reviewing and testing pulls

[Ketil Malde]

Kevin Smith <yarcs at qualitycode.com> writes:

> First, I have already been creating ad-hoc branches here and
> there. And, frankly, it is *very* easy to get lost and forget which
> ones are interesting and which ones are trash. I need to be more
> disciplined with this in general, and especially if using this
> technique to merge in other people's patches.

I think subversion recommends having top-level directories "trunk",
"tags" and "branches".  I also added "done" and "dead-ends" to this. 

When developing new functionality, I branched (copied) the trunk to a
new directory in "branches".  When done, I merged the changes back
into "trunk", and moved the branch to "done".  If I decided to scrap
the branch, I moved it to "dead-ends".

The nice thing about using Subversion was that the whole thing could
be backed up by backing up the repository database.  What is the best
way to back up darcs (with a cluster of ad-hoc repos)? 

-kzm
-- 
If I haven't seen further, it is by standing in the footprints of giants