18
18
Written in Haskell.
20
Breaking commits into hunks at commit time is interesting, but I think
21
not totally necessary. Sometimes it won't break hunks where you want
20
24
A really simple pre-commit check hook is remarkably useful.
22
26
http://www.scannedinavian.org/DarcsWiki/DifferencesFromArch
26
Sometimes useful to be able to set email per-branch, for people who
27
work on different projects under different personas.
40
38
This can perhaps be inferred by a smart 3-way merge tool. Certainly
41
39
you could have it do sub-line merges.
46
darcs allows you to commit only some of the changes to a single file.
47
This is like the common feature of commiting only a subset of changed
48
files, but taken to a higher level.
50
It is useful more often than one might think: it is common to fix some
51
documentation 'on the wing' and while strictly it should be in a
52
separate commit it is not always worth the hassle to back out changes,
53
fix the docs, then do the real change. Similarly for making a
56
Although the idea is very good, the current darcs implementation is
57
limited to selecting by patch hunk, which means that neighbouring
58
changes cannot be separated. Fixing this probably means having some
59
kind of pluggable GUI to build the file-to-be-committed or an edited
60
patch, possibly using something like meld, emacs, or dirdiff. Another
61
approach some people might like is editing the diff file to chop out
64
I don't think this needs to be on by default, as it is in darcs. It
65
is usual to commit all the changes.
67
For this to work safely, it is good to have a commit hook that
68
builds/tests the tree. Of course this needs to be evaluated against
69
the tree as it will be committed (taking account of partial commits),
added
removed
doc/darcs.txt
