Thu, 20 Mar 2008 22:41:40 +0100 util: test fileno() availability in win32 set_binary()
Patrick Mezard <pmezard@gmail.com> [Thu, 20 Mar 2008 22:41:40 +0100] rev 6330
util: test fileno() availability in win32 set_binary() Fix suggested by Alexander Belchenko <bialix@ukr.net>
Thu, 20 Mar 2008 15:59:54 -0500 tests: fix repeatability for test-filebranch with dirstate granularity
Matt Mackall <mpm@selenic.com> [Thu, 20 Mar 2008 15:59:54 -0500] rev 6329
tests: fix repeatability for test-filebranch with dirstate granularity
Thu, 20 Mar 2008 14:14:15 -0500 tests: remove some unnecessary sleeps
Matt Mackall <mpm@selenic.com> [Thu, 20 Mar 2008 14:14:15 -0500] rev 6328
tests: remove some unnecessary sleeps
Thu, 20 Mar 2008 13:53:59 -0500 dirstate: refactor granularity code, add a test
Matt Mackall <mpm@selenic.com> [Thu, 20 Mar 2008 13:53:59 -0500] rev 6327
dirstate: refactor granularity code, add a test - rename option dirstate.granularity - move option reading into .write() - add a simple test
Wed, 19 Mar 2008 17:55:21 -0300 dirstate: ignore stat data for files that were updated too recently
Alexis S. L. Carvalho <alexis@cecm.usp.br> [Wed, 19 Mar 2008 17:55:21 -0300] rev 6326
dirstate: ignore stat data for files that were updated too recently This should fix the race where hg commit foo <change foo without changing its size> happens in the same second and status is fooled into thinking foo is clean. A configuration item is used to determine the timeout, since different filesystems may have different requirements (I think VFAT needs 3s, while most Unix filesystems are fine with 1s).
Thu, 20 Mar 2008 11:12:35 -0500 pager: remove pager code from core
Matt Mackall <mpm@selenic.com> [Thu, 20 Mar 2008 11:12:35 -0500] rev 6325
pager: remove pager code from core
Thu, 20 Mar 2008 11:12:35 -0500 pager: further simplify code, clean up comments
Matt Mackall <mpm@selenic.com> [Thu, 20 Mar 2008 11:12:35 -0500] rev 6324
pager: further simplify code, clean up comments
Thu, 20 Mar 2008 00:57:14 +0100 Use the pager given by the environment to display long output
David Soria Parra <dsp@php.net> [Thu, 20 Mar 2008 00:57:14 +0100] rev 6323
Use the pager given by the environment to display long output Unix systems usually have a PAGER environment variable set. If it is set, mercurial will use the pager application to display output. Two configuration variables are available to influence the behaviour of the pager: pager.application sets the application to be used pager.quiet silences Broken Pipe errors that might occur when the user quits the pager before mercurial finished to write the output
(0) -3000 -1000 -300 -100 -30 -10 -8 +8 +10 +30 +100 +300 +1000 +3000 +10000 +30000 tip