sapling/tests/test-diffdir.t

  $ hg init
  $ touch a
  $ hg add a
  $ hg ci -m "a"

  $ echo 123 > b
  $ hg add b
  $ hg diff --nodates
  diff -r 3903775176ed b
  --- /dev/null
  +++ b/b
  @@ -0,0 +1,1 @@
  +123

  $ hg diff --nodates -r tip
  diff -r 3903775176ed b
  --- /dev/null
  +++ b/b
  @@ -0,0 +1,1 @@
  +123

  $ echo foo > a
  $ hg diff --nodates
  diff -r 3903775176ed a
  --- a/a
  +++ b/a
  @@ -0,0 +1,1 @@
  +foo
  diff -r 3903775176ed b
  --- /dev/null
  +++ b/b
  @@ -0,0 +1,1 @@
  +123

  $ hg diff -r ""
  abort: 00changelog.i@: ambiguous identifier!
  [255]
  $ hg diff -r tip -r ""
  abort: 00changelog.i@: ambiguous identifier!
  [255]
tests: unify test-diffdir 2010-08-17 16:27:48 +04:00			`$ hg init`
			`$ touch a`
			`$ hg add a`
tests: remove unneeded -d flags Many tests fixed the commit date of their changesets at '1000000 0' or similar. However testing with "Mon Jan 12 13:46:40 1970 +0000" is not better than testing with "Thu Jan 01 00:00:00 1970 +0000", which is the default run-tests.py installs. Removing the unnecessary flag removes some clutter and will hopefully make it clearer what the tests are really trying to test. Some tests did not even change their output when the dates were changed, in which case the -d flag was truly irrelevant. Dates used in sequence (such as '0 0', '1 0', etc...) were left alone since they may make the test easier to understand. 2010-09-03 01:22:51 +04:00			`$ hg ci -m "a"`
tests: unify test-diffdir 2010-08-17 16:27:48 +04:00
			`$ echo 123 > b`
			`$ hg add b`
			`$ hg diff --nodates`
tests: remove unneeded -d flags Many tests fixed the commit date of their changesets at '1000000 0' or similar. However testing with "Mon Jan 12 13:46:40 1970 +0000" is not better than testing with "Thu Jan 01 00:00:00 1970 +0000", which is the default run-tests.py installs. Removing the unnecessary flag removes some clutter and will hopefully make it clearer what the tests are really trying to test. Some tests did not even change their output when the dates were changed, in which case the -d flag was truly irrelevant. Dates used in sequence (such as '0 0', '1 0', etc...) were left alone since they may make the test easier to understand. 2010-09-03 01:22:51 +04:00			`diff -r 3903775176ed b`
tests: unify test-diffdir 2010-08-17 16:27:48 +04:00			`--- /dev/null`
			`+++ b/b`
			`@@ -0,0 +1,1 @@`
			`+123`

			`$ hg diff --nodates -r tip`
tests: remove unneeded -d flags Many tests fixed the commit date of their changesets at '1000000 0' or similar. However testing with "Mon Jan 12 13:46:40 1970 +0000" is not better than testing with "Thu Jan 01 00:00:00 1970 +0000", which is the default run-tests.py installs. Removing the unnecessary flag removes some clutter and will hopefully make it clearer what the tests are really trying to test. Some tests did not even change their output when the dates were changed, in which case the -d flag was truly irrelevant. Dates used in sequence (such as '0 0', '1 0', etc...) were left alone since they may make the test easier to understand. 2010-09-03 01:22:51 +04:00			`diff -r 3903775176ed b`
tests: unify test-diffdir 2010-08-17 16:27:48 +04:00			`--- /dev/null`
			`+++ b/b`
			`@@ -0,0 +1,1 @@`
			`+123`

			`$ echo foo > a`
			`$ hg diff --nodates`
tests: remove unneeded -d flags Many tests fixed the commit date of their changesets at '1000000 0' or similar. However testing with "Mon Jan 12 13:46:40 1970 +0000" is not better than testing with "Thu Jan 01 00:00:00 1970 +0000", which is the default run-tests.py installs. Removing the unnecessary flag removes some clutter and will hopefully make it clearer what the tests are really trying to test. Some tests did not even change their output when the dates were changed, in which case the -d flag was truly irrelevant. Dates used in sequence (such as '0 0', '1 0', etc...) were left alone since they may make the test easier to understand. 2010-09-03 01:22:51 +04:00			`diff -r 3903775176ed a`
tests: unify test-diffdir 2010-08-17 16:27:48 +04:00			`--- a/a`
			`+++ b/a`
			`@@ -0,0 +1,1 @@`
			`+foo`
tests: remove unneeded -d flags Many tests fixed the commit date of their changesets at '1000000 0' or similar. However testing with "Mon Jan 12 13:46:40 1970 +0000" is not better than testing with "Thu Jan 01 00:00:00 1970 +0000", which is the default run-tests.py installs. Removing the unnecessary flag removes some clutter and will hopefully make it clearer what the tests are really trying to test. Some tests did not even change their output when the dates were changed, in which case the -d flag was truly irrelevant. Dates used in sequence (such as '0 0', '1 0', etc...) were left alone since they may make the test easier to understand. 2010-09-03 01:22:51 +04:00			`diff -r 3903775176ed b`
tests: unify test-diffdir 2010-08-17 16:27:48 +04:00			`--- /dev/null`
			`+++ b/b`
			`@@ -0,0 +1,1 @@`
			`+123`

			`$ hg diff -r ""`
			`abort: 00changelog.i@: ambiguous identifier!`
tests: add exit codes to unified tests 2010-09-17 02:51:32 +04:00			`[255]`
tests: unify test-diffdir 2010-08-17 16:27:48 +04:00			`$ hg diff -r tip -r ""`
			`abort: 00changelog.i@: ambiguous identifier!`
tests: add exit codes to unified tests 2010-09-17 02:51:32 +04:00			`[255]`