Hi, On Thu, 27 Dec 2012, Martin Quinson wrote: > You mean that when a patch is pushed, the same timestamp (which one, > actually?) must be set on all modified files?
Yes. > It seems rather improbable that anything else happens, doesn't it? I > mean all these files are modified automatically, and it seems very > probable to me that they all get the same mtime. But I may well be wrong > on this. Indeed, you are wrong. mtime is precise up to nanoseconds with recent filesystems and it's unlikely that the mtime matches even when the files are modified in a single patch call. > Or maybe you mean that the files timestamps should be restored to their > old value when the patch is removed? I don't think so. > Anyway, the timestamp handling improved a lot in quilt in the last four > years (!), and I would appreciate if you could double-check that the > faulty behavior is still there while elaborating what the right behavior > should be. I think that the problem is still here. I don't see anything in quilt/push.in that would reset the mtime after the patch has been applied. Cheers, -- Raphaël Hertzog ◈ Debian Developer Get the Debian Administrator's Handbook: → http://debian-handbook.info/get/ -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
