Show More
@@ -1,30 +1,30 b'' | |||
|
1 | 1 | #!/bin/sh |
|
2 | 2 | |
|
3 | 3 | hg init |
|
4 | 4 | echo a > a |
|
5 | 5 | hg add a |
|
6 | 6 | hg commit -m "1" -d "1000000 0" |
|
7 | 7 | hg status |
|
8 | 8 | hg copy a b |
|
9 | 9 | hg status |
|
10 | 10 | hg --debug commit -m "2" -d "1000000 0" |
|
11 | 11 | echo "we should see two history entries" |
|
12 | 12 | hg history -v |
|
13 | 13 | echo "we should see one log entry for a" |
|
14 | 14 | hg log a |
|
15 | 15 | echo "this should show a revision linked to changeset 0" |
|
16 | 16 | hg debugindex .hg/data/a.i |
|
17 | 17 | echo "we should see one log entry for b" |
|
18 | 18 | hg log b |
|
19 | 19 | echo "this should show a revision linked to changeset 1" |
|
20 | 20 | hg debugindex .hg/data/b.i |
|
21 | 21 | |
|
22 | 22 | echo "this should show the rename information in the metadata" |
|
23 | 23 | hg debugdata .hg/data/b.d 0 | head -3 | tail -2 |
|
24 | 24 | |
|
25 |
$TESTDIR/md5sum.py .hg/data/b. |
|
|
25 | $TESTDIR/md5sum.py .hg/data/b.i | |
|
26 | 26 | hg cat b > bsum |
|
27 | 27 | $TESTDIR/md5sum.py bsum |
|
28 | 28 | hg cat a > asum |
|
29 | 29 | $TESTDIR/md5sum.py asum |
|
30 | 30 | hg verify |
@@ -1,51 +1,51 b'' | |||
|
1 | 1 | A b |
|
2 | 2 | b |
|
3 | 3 | b: copy a:b789fdd96dc2f3bd229c1dd8eedf0fc60e2b68e3 |
|
4 | 4 | we should see two history entries |
|
5 | 5 | changeset: 1:386a3cc01532710ca78aed9a54fa2f459c04f29c |
|
6 | 6 | tag: tip |
|
7 | 7 | user: test |
|
8 | 8 | date: Mon Jan 12 13:46:40 1970 +0000 |
|
9 | 9 | files: b |
|
10 | 10 | description: |
|
11 | 11 | 2 |
|
12 | 12 | |
|
13 | 13 | |
|
14 | 14 | changeset: 0:33aaa84a386bd609094aeb21a97c09436c482ef1 |
|
15 | 15 | user: test |
|
16 | 16 | date: Mon Jan 12 13:46:40 1970 +0000 |
|
17 | 17 | files: a |
|
18 | 18 | description: |
|
19 | 19 | 1 |
|
20 | 20 | |
|
21 | 21 | |
|
22 | 22 | we should see one log entry for a |
|
23 | 23 | changeset: 0:33aaa84a386b |
|
24 | 24 | user: test |
|
25 | 25 | date: Mon Jan 12 13:46:40 1970 +0000 |
|
26 | 26 | summary: 1 |
|
27 | 27 | |
|
28 | 28 | this should show a revision linked to changeset 0 |
|
29 | 29 | rev offset length base linkrev nodeid p1 p2 |
|
30 | 30 | 0 0 3 0 0 b789fdd96dc2 000000000000 000000000000 |
|
31 | 31 | we should see one log entry for b |
|
32 | 32 | changeset: 1:386a3cc01532 |
|
33 | 33 | tag: tip |
|
34 | 34 | user: test |
|
35 | 35 | date: Mon Jan 12 13:46:40 1970 +0000 |
|
36 | 36 | summary: 2 |
|
37 | 37 | |
|
38 | 38 | this should show a revision linked to changeset 1 |
|
39 | 39 | rev offset length base linkrev nodeid p1 p2 |
|
40 | 40 | 0 0 65 0 1 9a263dd772e0 000000000000 000000000000 |
|
41 | 41 | this should show the rename information in the metadata |
|
42 | 42 | copyrev: b789fdd96dc2f3bd229c1dd8eedf0fc60e2b68e3 |
|
43 | 43 | copy: a |
|
44 | 566e338d09a089ba737c21e0d3759980 .hg/data/b.d | |
|
44 | ed156f22f0a6fde642de0b5eba0cbbb2 .hg/data/b.i | |
|
45 | 45 | 60b725f10c9c85c70d97880dfe8191b3 bsum |
|
46 | 46 | 60b725f10c9c85c70d97880dfe8191b3 asum |
|
47 | 47 | checking changesets |
|
48 | 48 | checking manifests |
|
49 | 49 | crosschecking files in changesets and manifests |
|
50 | 50 | checking files |
|
51 | 51 | 2 files, 2 changesets, 2 total revisions |
@@ -1,10 +1,9 b'' | |||
|
1 | 1 | 0 |
|
2 | 2 | 0 |
|
3 | 3 | adding changesets |
|
4 | 4 | killed! |
|
5 | 5 | transaction abort! |
|
6 | 6 | rollback completed |
|
7 | 00changelog.d | |
|
8 | 7 | 00changelog.i |
|
9 | 8 | data |
|
10 | 9 | journal.dirstate |
@@ -1,15 +1,15 b'' | |||
|
1 | 1 | #!/bin/sh |
|
2 | 2 | |
|
3 | 3 | hg init |
|
4 | 4 | echo foo > a |
|
5 | 5 | hg add a |
|
6 | 6 | hg commit -m "1" -d "1000000 0" |
|
7 | 7 | hg verify |
|
8 |
chmod -r .hg/data/a. |
|
|
8 | chmod -r .hg/data/a.i | |
|
9 | 9 | hg verify 2>/dev/null || echo verify failed |
|
10 |
chmod +r .hg/data/a. |
|
|
10 | chmod +r .hg/data/a.i | |
|
11 | 11 | hg verify 2>/dev/null || echo verify failed |
|
12 |
chmod -w .hg/data/a. |
|
|
12 | chmod -w .hg/data/a.i | |
|
13 | 13 | echo barber > a |
|
14 | 14 | hg commit -m "2" -d "1000000 0" 2>/dev/null || echo commit failed |
|
15 | 15 |
General Comments 0
You need to be logged in to leave comments.
Login now