44 |
44 |
45 |
45 |
46 Introduction |
46 Introduction |
47 ------------ |
47 ------------ |
48 |
48 |
49 Mercurial http://www.selenic.com/mercurial belongs to the current |
49 Mercurial http://www.selenic.com/mercurial belongs to source code |
50 generation of source code management systems that follow the so-called |
50 management systems that follow the so-called paradigm of "distributed |
51 paradigm of "distributed version control". This is a terrific name |
51 version control". This means plain revision control without the |
52 for plain revision control without the legacy of CVS or SVN. See also |
52 legacy of CVS or SVN (and without the extra complexity introduced by |
53 http://hginit.com/ for an introduction to the main ideas. The |
53 git). See also http://hginit.com/ for an introduction to the main |
54 Mercurial book http://hgbook.red-bean.com/ explains many more details. |
54 ideas. The Mercurial book http://hgbook.red-bean.com/ explains many |
55 |
55 more details. |
56 Mercurial offers great flexibility in organizing the flow of changes, |
56 |
|
57 Mercurial offers some flexibility in organizing the flow of changes, |
57 both between individual developers and designated pull/push areas that |
58 both between individual developers and designated pull/push areas that |
58 are shared with others. This additional power demands some additional |
59 are shared with others. This additional freedom demands additional |
59 responsibility to maintain a certain development process that fits to |
60 responsibility to maintain a certain development process that fits to |
60 a particular project. |
61 a particular project. |
61 |
62 |
62 Regular Mercurial operations are strictly monotonic, where changeset |
63 Regular Mercurial operations are strictly monotonic, where changeset |
63 transactions are only added, but never deleted or mutated. There are |
64 transactions are only added, but never deleted or mutated. There are |
292 Isabelle testboard at TUM. In contrast, the subsequent command-line |
293 Isabelle testboard at TUM. In contrast, the subsequent command-line |
293 examples are for tests on the local machine: |
294 examples are for tests on the local machine: |
294 |
295 |
295 ./bin/isabelle build -a #regular test |
296 ./bin/isabelle build -a #regular test |
296 |
297 |
297 ./bin/isabelle build -a -o document=pdf #test with document preparation |
298 ./bin/isabelle build -a -o document=pdf #test with document preparation (optional) |
298 |
299 |
299 ./bin/isabelle build -a -j2 -o threads=4 #test on multiple cores (example) |
300 ./bin/isabelle build -a -j2 -o threads=4 #test on multiple cores (example) |
300 |
301 |
301 See also the chapter on Isabelle sessions and build management in the |
302 See also the chapter on Isabelle sessions and build management in the |
302 "system" manual. |
303 "system" manual. |