This is an archive of the discontinued Mercurial Phabricator instance.

	> sys.stdout.write(sys.stdin.read())			> sys.stdout.write(sys.stdin.read())
	> EOF			> EOF

	$ hg fix --working-dir -r "all()" \			$ hg fix --working-dir -r "all()" \
	> --config "fix.log:command=\"$PYTHON\" \"$LOGGER\" {rootpath}" \			> --config "fix.log:command=\"$PYTHON\" \"$LOGGER\" {rootpath}" \
	> --config "fix.log:pattern=glob:**.log"			> --config "fix.log:pattern=glob:**.log"

	$ cat $LOGFILE \| sort \| uniq -c			$ cat $LOGFILE \| sort \| uniq -c
	4 bar.log			\s*4 bar.log (re)
	4 baz.log			\s*4 baz.log (re)
	3 foo.log			\s*3 foo.log (re)
	2 qux.log			\s*2 qux.log (re)

	$ cd ..			$ cd ..

	For tools that support line ranges, it's wrong to blindly re-use fixed file			For tools that support line ranges, it's wrong to blindly re-use fixed file
	content for the same file revision if it appears twice with different baserevs,			content for the same file revision if it appears twice with different baserevs,
	because the line ranges could be different. Since computing line ranges is			because the line ranges could be different. Since computing line ranges is
	ambiguous, this isn't a matter of correctness, but it affects the usability of			ambiguous, this isn't a matter of correctness, but it affects the usability of
	this extension. It could maybe be simpler if baserevs were computed on a			this extension. It could maybe be simpler if baserevs were computed on a

tests: fix test-fix on NetBSDClosedPublic