Rev 4939: NEWS about fixing bug #488724 in http://bazaar.launchpad.net/~jameinel/bzr/2.1.0rc1-set-mtime

John Arbash Meinel john at arbash-meinel.com
Tue Jan 5 21:41:28 GMT 2010


At http://bazaar.launchpad.net/~jameinel/bzr/2.1.0rc1-set-mtime

------------------------------------------------------------
revno: 4939
revision-id: john at arbash-meinel.com-20100105214109-4jd065q8anu53r3o
parent: john at arbash-meinel.com-20100105213830-g3lquxafftzzqlmm
committer: John Arbash Meinel <john at arbash-meinel.com>
branch nick: 2.1.0rc1-set-mtime
timestamp: Tue 2010-01-05 15:41:09 -0600
message:
  NEWS about fixing bug #488724
-------------- next part --------------
=== modified file 'NEWS'
--- a/NEWS	2010-01-05 16:55:12 +0000
+++ b/NEWS	2010-01-05 21:41:09 +0000
@@ -64,6 +64,14 @@
 * Listen to the SIGWINCH signal to update the terminal width.
   (Vincent Ladeuil, #316357)
 
+* Operations which update the working tree should now create all files
+  with the same mtime. So if you version a generated file and its source,
+  when updating you should get the same mtime for both files. We use
+  ``SetFileInformationByHandle`` on Windows, and ``futimes()`` on POSIX
+  systems to achieve this effect. This only works when extensions are
+  compiled as pure-python does not expose similar functionality.
+  (John Arbash Meinel, #488724)
+
 * The 2a format wasn't properly restarting autopacks when something
   changed underneath it (like another autopack). Now concurrent
   autopackers will properly succeed. (John Arbash Meinel, #495000)



More information about the bazaar-commits mailing list