Next: , Previous: Pulling new patches, Up: Top

6 Recording a patch

What is called “committing” in some other version control systems, is called “recording” in darcs. Before doing that, you may want to review your local changes.


Find changes in repo and print them.

This command compares the files in your working directory to the pristine tree; see Working directory layout. “Boring” files are ignored; see Boring files. New files in your tree are automatically included in the diff output, unless they are “boring”.

— Function: DARCS:RECORD-CHANGES repo name author date log

Interactively ask which changes to repo to record.

repo is the local directory containing the repository. name is the “name” of the patch, usually a one-line summary of the change. author is an author identifier, usually an e-mail address. date is usually the keyword :NOW, but can also be a string in YYYYMMDDHHMMSS format. log is a string (possibly multi-line) containing a longer description of the patch, or NIL.

Unlike many other version control systems, you can commit just some of the changes in a file, by answering yes to some hunks and no to others.