Show More
@@ -579,7 +579,7 Check that bisect does not break on obso | |||
|
579 | 579 | tip is obsolete |
|
580 | 580 | --------------------- |
|
581 | 581 | |
|
582 |
$ hg debugobsolete `hg id - |
|
|
582 | $ hg debugobsolete `hg id -T "{node}" -r tip` | |
|
583 | 583 | 1 new obsolescence markers |
|
584 | 584 | obsoleted 1 changesets |
|
585 | 585 | $ hg bisect --reset |
@@ -608,7 +608,7 Rewritten commits should not crash | |||
|
608 | 608 | reverting a |
|
609 | 609 | $ hg commit -m 'msg 30 -- fixed' |
|
610 | 610 | created new head |
|
611 |
$ hg debugobsolete `hg id - |
|
|
611 | $ hg debugobsolete `hg id -T "{node}" -r 30` `hg id -T "{node}" -r .` | |
|
612 | 612 | 1 new obsolescence markers |
|
613 | 613 | obsoleted 1 changesets |
|
614 | 614 | $ hg bisect |
@@ -35,26 +35,26 censored node C1, second C2, and so on | |||
|
35 | 35 | $ echo 'Tainted file' > target |
|
36 | 36 | $ echo 'Passwords: hunter2' >> target |
|
37 | 37 | $ hg ci -m taint target |
|
38 |
$ C1=`hg id - |
|
|
38 | $ C1=`hg id -r . -T "{node}"` | |
|
39 | 39 | |
|
40 | 40 | $ echo 'hunter3' >> target |
|
41 | 41 | $ echo 'Normal file v2' > bystander |
|
42 | 42 | $ hg ci -m moretaint target bystander |
|
43 |
$ C2=`hg id - |
|
|
43 | $ C2=`hg id -r . -T "{node}"` | |
|
44 | 44 | |
|
45 | 45 | Add a new sanitized versions to correct our mistake. Name the first head H1, |
|
46 | 46 | the second head H2, and so on |
|
47 | 47 | |
|
48 | 48 | $ echo 'Tainted file is now sanitized' > target |
|
49 | 49 | $ hg ci -m sanitized target |
|
50 |
$ H1=`hg id - |
|
|
50 | $ H1=`hg id -r . -T "{node}"` | |
|
51 | 51 | |
|
52 | 52 | $ hg update -r $C2 |
|
53 | 53 | 1 files updated, 0 files merged, 0 files removed, 0 files unresolved |
|
54 | 54 | $ echo 'Tainted file now super sanitized' > target |
|
55 | 55 | $ hg ci -m 'super sanitized' target |
|
56 | 56 | created new head |
|
57 |
$ H2=`hg id - |
|
|
57 | $ H2=`hg id -r . -T "{node}"` | |
|
58 | 58 | |
|
59 | 59 | Verify target contents before censorship at each revision |
|
60 | 60 | |
@@ -239,7 +239,7 with the file censored, but we can't cen | |||
|
239 | 239 | $ C3=$H1 |
|
240 | 240 | $ echo 'advanced head H1' > target |
|
241 | 241 | $ hg ci -m 'advance head H1' target |
|
242 |
$ H1=`hg id - |
|
|
242 | $ H1=`hg id -r . -T "{node}"` | |
|
243 | 243 | $ hg --config extensions.censor= censor -r $C3 target |
|
244 | 244 | checking for the censored content in 2 heads |
|
245 | 245 | checking for the censored content in the working directory |
@@ -262,7 +262,7 Revisions present in repository heads ma | |||
|
262 | 262 | [255] |
|
263 | 263 | $ echo 'twiddling thumbs' > bystander |
|
264 | 264 | $ hg ci -m 'bystander commit' |
|
265 |
$ H2=`hg id - |
|
|
265 | $ H2=`hg id -r . -T "{node}"` | |
|
266 | 266 | $ hg --config extensions.censor= censor -r "$H2^" target |
|
267 | 267 | checking for the censored content in 2 heads |
|
268 | 268 | abort: cannot censor file in heads (efbe78065929) |
@@ -273,7 +273,7 Cannot censor working directory | |||
|
273 | 273 | |
|
274 | 274 | $ echo 'seriously no passwords' > target |
|
275 | 275 | $ hg ci -m 'extend second head arbitrarily' target |
|
276 |
$ H2=`hg id - |
|
|
276 | $ H2=`hg id -r . -T "{node}"` | |
|
277 | 277 | $ hg update -r "$H2^" |
|
278 | 278 | 1 files updated, 0 files merged, 0 files removed, 0 files unresolved |
|
279 | 279 | $ hg --config extensions.censor= censor -r . target |
@@ -290,7 +290,7 Can re-add file after being deleted + ce | |||
|
290 | 290 | $ C4=$H2 |
|
291 | 291 | $ hg rm target |
|
292 | 292 | $ hg ci -m 'delete target so it may be censored' |
|
293 |
$ H2=`hg id - |
|
|
293 | $ H2=`hg id -r . -T "{node}"` | |
|
294 | 294 | $ hg --config extensions.censor= censor -r $C4 target |
|
295 | 295 | checking for the censored content in 2 heads |
|
296 | 296 | checking for the censored content in the working directory |
@@ -301,7 +301,7 Can re-add file after being deleted + ce | |||
|
301 | 301 | $ echo 'fresh start' > target |
|
302 | 302 | $ hg add target |
|
303 | 303 | $ hg ci -m reincarnated target |
|
304 |
$ H2=`hg id - |
|
|
304 | $ H2=`hg id -r . -T "{node}"` | |
|
305 | 305 | $ hg cat -r $H2 target | head -n 10 |
|
306 | 306 | fresh start |
|
307 | 307 | $ hg cat -r "$H2^" target | head -n 10 |
@@ -318,11 +318,11 Can censor enough revision to move back | |||
|
318 | 318 | 8 ??? yes file target (glob) (revlogv1 !) |
|
319 | 319 | $ $TESTDIR/seq.py 4000 | $TESTDIR/sha256line.py > target |
|
320 | 320 | $ hg ci -m 'add 100k passwords' |
|
321 |
$ H2=`hg id - |
|
|
321 | $ H2=`hg id -r . -T "{node}"` | |
|
322 | 322 | $ C5=$H2 |
|
323 | 323 | $ hg revert -r "$H2^" target |
|
324 | 324 | $ hg ci -m 'cleaned 100k passwords' |
|
325 |
$ H2=`hg id - |
|
|
325 | $ H2=`hg id -r . -T "{node}"` | |
|
326 | 326 | $ hg debugrevlogstats | grep target |
|
327 | 327 | rev-count data-size inl type target |
|
328 | 328 | 10 ?????? no file target (glob) |
@@ -399,11 +399,11 Censored nodes can be pushed if they cen | |||
|
399 | 399 | $ echo 'Passwords: hunter2hunter2' > target |
|
400 | 400 | $ hg ci -m 're-add password from clone' target |
|
401 | 401 | created new head |
|
402 |
$ H3=`hg id - |
|
|
402 | $ H3=`hg id -r . -T "{node}"` | |
|
403 | 403 | $ REV=$H3 |
|
404 | 404 | $ echo 'Re-sanitized; nothing to see here' > target |
|
405 | 405 | $ hg ci -m 're-sanitized' target |
|
406 |
$ H2=`hg id - |
|
|
406 | $ H2=`hg id -r . -T "{node}"` | |
|
407 | 407 | $ CLEANREV=$H2 |
|
408 | 408 | $ hg cat -r $REV target | head -n 10 |
|
409 | 409 | Passwords: hunter2hunter2 |
@@ -556,17 +556,17 Censoring a revision that is used as del | |||
|
556 | 556 | $ echo root > target |
|
557 | 557 | $ hg add target |
|
558 | 558 | $ hg commit -m root |
|
559 |
$ B0=`hg id - |
|
|
559 | $ B0=`hg id -r . -T "{node}"` | |
|
560 | 560 | $ for x in `"$PYTHON" $TESTDIR/seq.py 0 50000` |
|
561 | 561 | > do |
|
562 | 562 | > echo "Password: hunter$x" >> target |
|
563 | 563 | > done |
|
564 | 564 | $ hg ci -m 'write a long file' |
|
565 |
$ B1=`hg id - |
|
|
565 | $ B1=`hg id -r . -T "{node}"` | |
|
566 | 566 | $ echo 'small change (should create a delta)' >> target |
|
567 | 567 | $ hg ci -m 'create a delta over the password' |
|
568 | 568 | (should show that the last revision is a delta, not a snapshot) |
|
569 |
$ B2=`hg id - |
|
|
569 | $ B2=`hg id -r . -T "{node}"` | |
|
570 | 570 | |
|
571 | 571 | Make sure the last revision is a delta against the revision we will censor |
|
572 | 572 |
@@ -15,11 +15,11 | |||
|
15 | 15 | $ echo a >> a |
|
16 | 16 | $ hg ci -Am addb |
|
17 | 17 | adding b |
|
18 |
$ PARENTID1=`hg id - |
|
|
18 | $ PARENTID1=`hg id -r . -T "{node}"` | |
|
19 | 19 | $ echo c > c |
|
20 | 20 | $ hg ci -Am addc |
|
21 | 21 | adding c |
|
22 |
$ PARENTID2=`hg id - |
|
|
22 | $ PARENTID2=`hg id -r . -T "{node}"` | |
|
23 | 23 | $ cd .. |
|
24 | 24 | $ glog -R repo1 |
|
25 | 25 | @ 2:e55c719b85b6 "addc" files: c |
@@ -38,10 +38,10 | |||
|
38 | 38 | adding d |
|
39 | 39 | $ INVALIDID1=afd12345af |
|
40 | 40 | $ INVALIDID2=28173x36ddd1e67bf7098d541130558ef5534a86 |
|
41 |
$ CHILDID1=`hg id - |
|
|
41 | $ CHILDID1=`hg id -r . -T "{node}"` | |
|
42 | 42 | $ echo d >> d |
|
43 | 43 | $ hg ci -Am changed |
|
44 |
$ CHILDID2=`hg id - |
|
|
44 | $ CHILDID2=`hg id -r . -T "{node}"` | |
|
45 | 45 | $ echo e > e |
|
46 | 46 | $ hg ci -Am adde |
|
47 | 47 | adding e |
@@ -766,7 +766,7 test hidden changeset are not cloned as | |||
|
766 | 766 | > EOF |
|
767 | 767 | |
|
768 | 768 | (making a changeset hidden; H in that case) |
|
769 |
$ hg debugobsolete `hg id - |
|
|
769 | $ hg debugobsolete `hg id -T "{node}" -r 5` | |
|
770 | 770 | 1 new obsolescence markers |
|
771 | 771 | obsoleted 1 changesets |
|
772 | 772 | |
@@ -1018,7 +1018,7 Commit is hidden as expected | |||
|
1018 | 1018 | The hidden commit is an orphan but doesn't show up without --hidden |
|
1019 | 1019 | And internal changesets are not considered for unstability. |
|
1020 | 1020 | |
|
1021 |
$ hg debugobsolete `hg id - |
|
|
1021 | $ hg debugobsolete `hg id -T "{node}" -r 0` | |
|
1022 | 1022 | 1 new obsolescence markers |
|
1023 | 1023 | obsoleted 1 changesets |
|
1024 | 1024 | $ hg --hidden log -G -r '(0::) - 0' |
General Comments 0
You need to be logged in to leave comments.
Login now