>>>>> "Simon" == Simon Marlow <[EMAIL PROTECTED]> writes:
Simon> What are the recommendations to definitely avoid darcs
Simon> disappearing down a blackhole with your repository in the
Simon> future?
1. Patches to files that mostly get changed in the same place should
be separated out from everything else. ChangeLogs are the canonical
example (so much so that most SCMs deprecate the practice of keeping a
separate log file in favor of using SCM-generated logs). However,
NEWS, AUTHORS, anything with a time-stamp or revision number (think
copyright notice if you have an assignment policy) can have this kind
of issue.
2. Keep patches small where possible.
--
School of Systems and Information Engineering http://turnbull.sk.tsukuba.ac.jp
University of Tsukuba Tennodai 1-1-1 Tsukuba 305-8573 JAPAN
Ask not how you can "do" free software business;
ask what your business can "do for" free software.
_______________________________________________
darcs-users mailing list
[email protected]
http://www.abridgegame.org/mailman/listinfo/darcs-users
