Understanding Darcs/Working with others

The commandsEdit

getEdit

darcs get makes a copy of an entire darcs repository. Note that we only get the recorded patches (and pristine tree), not any of the pending stuff.

during darcs get

pull/pushEdit

darcs pull copies from some other repository patches that you do not have. The patches are applied to your pristine tree and working directory. This may cause changes to be merged. Note that darcs push does the same thing, but in the other direction.

during darcs pull

sendEdit

Darcs send is sort of like push, only it doesn't actually apply the patches anywhere. Instead it generates a handy email to the person or people who own the repository. If it can't figure out who owns the repository, it will let you send to any email address you want. Note that you can also pass the -o command to "send" into a file, rather than a mail.

applyEdit

Apply is what you do to a patch that somebody darcs sends to you. You can also use it for the files you generated via send -o. Note: push is actually just apply in disguise, but with all the boring work of copying files over being done for you.

putEdit

Put enables to copy a local repository to remote location (for instance, via ssh). Think of put as the opposite of get.

Dealing with conflictsEdit

So you pulled a patch and you got a conflict. What do you do? See the chapter Dealing with conflicts

Next Page: Reviewing your work | Previous Page: Making changes

Home: Understanding Darcs

Last modified on 2 September 2011, at 17:32