now create the files, do some work and after that:
$> darcs add file1 file2 file3 ... $> darcs record -am 'some comments here'
'darcs whatsnew' lists unrecorded changes to the working tree
'darcs changes' will show you your patches
$> darcs revert <FILENAME>
use a _darcs/pref/boring file
to see what boring files darcs is not managing, use
'darcs whatsnew -ls --boring'
in the boringfile:
if you want to match a directory and its contents, use a regex:
short answer: no way
in darcs branches and repositories are the same thing. so to create a branch, you have to use
$> darcs clone --to-patch='PATCHNAME' <REPO-DIR> $> darcs clone --tag <TAGNAME> <REPO-DIR>
$> darcs clone --to-match 'typeofmatch paramofmatch'
$> darcs put <REPO-DIR>creates a copy of the current repository
to set remote repository:
'darcs put --set-default </path/to/remote/repo>'and after that
to reproduce the state of a repository 'R' as it is at tag 't', use the command
$> darcs clone -tag t R
if you want to see which patches are missing from your or the remote repository, you can run
# patches you are missing $> darcs pull --dry-run # patches the remote repository is missing $> darcs push --dry-run
'darcs show tags'lists all tags in the current repository