darcs manual #vcs

๐Ÿ•’๏ธŽ - 2005-08-15

I just read the darcs manual, cover to cover (it's not that long). I've got a couple of repositories set up the way I like, and it seems fine.

One thing I would have liked a more thorough description of in the manual is the subject of branches. The paragraph about that is very thin. What is the best/usual approach to creating branches for release-versions and stuff like that?

Another thing I would like to have is to have an email generated on each checkin (push/send, I guess) with the diff of what has been put into the repository. (Only for some repositories - the ones I use in a centralized fashion (the ones I'd have a webinterface for as well), of course). After reading the manual I'm not sure how to do this (or where to look) or if it is possible at all.

The third thing I would love to have is a pcl-cvs-like interface for XEmacs.

Oh, and tiny things I don't know whether are "problems" or just user error: owner/group/permissions and symlink-handling, how?

And finally this slight annoyance:

 $ darcs changes
 Mon Aug 15 02:35:30 CEST 2005  Adam Sj\f8gren 
   * Initial import.


Update: The solution is in the manual - just set DARCS_DONT_ESCAPE_ISPRINT=1 ...

Add comment

To avoid spam many websites make you fill out a CAPTCHA, or log in via an account at a corporation such as Twitter, Facebook, Google or even Microsoft GitHub.

I have chosen to use a more old school method of spam prevention.

To post a comment here, you need to:

ยน Such as Thunderbird, Pan, slrn, tin or Gnus (part of Emacs).

Or, you can fill in this form: