Shouldn't this really be called the [darcs-developers] list? One thing I think would be very helpful to people trying to learn to use darcs is example work flows.
I think there is an assumption that people have used other repository software, and perhaps they have not. Moreover, the flow is different. It would be really helpful for example to show how one creates a "master" respository, then pulls/pushes to your working repos. And, then how one might actually create a "branch". We had hoped to keep our "master" repos on our shared web server which is backed up for us etc. However, we don't want to have to ftp into the site everytime to copy up the repos. So, we looked at the add-on darcs-server (which I realize isn't your project), but we have been unable to get it to work with either version of darcs, and the author is unreachable by the email on his site. Stuff like that, while not your fault, makes an impression, and also means it is less useful to people that want to focus on using the tool, not developing it. You guys seem like a knowledgeable bunch, and I really like darcs, so I hope that things pick up for you and the project takes off. If I take the time to make darcs-server like functionality work, I'll be sure to share. Patrick _______________________________________________ darcs-users mailing list [email protected] http://lists.osuosl.org/mailman/listinfo/darcs-users
