Hi Jani, On Mon, Nov 09, 2015 at 04:23:34PM +0200, Jani Nikula wrote: > On Sat, 07 Nov 2015, Lukas Wunner <lukas@xxxxxxxxx> wrote: > > three patches with fbdev deadlock & failure path fixes, > > each with Reviewed-by tag by Ville or Daniel, the third one > > with amended commit message as requested by Daniel in > > <20151030182818.GR16848@phenom.ffwll.local>. > Pushed all three to drm-intel-next-queued. Thanks for the patches and > review. Thank you! > Also, I don't know how you generate and send your patches, but even the > updated patches had dates of the original or very old versions of > them. Like [1] is June 30 although you sent it just a couple of days > ago. Please look into that. git format-patch tries to tunnel the author date through RFC 5322 by setting the Date-header to it. git send-email, which most people use, strips that and replaces it with the date of its invocation. I use msmtp instead of git send-email, which preserves the Date-header. When I edit commits, git commit --amend updates the commit date but not the author date. That's why you see these ancient timestamps. If you find that annoying I'll see to it that I modify the author date manually before sending out a new series. (At least in commits of my own. I try to avoid tampering with other people's commits.) > For future reference, please consider posting new versions of series as > new threads. This one got pretty messy in the end, with so many > different versions. Daniel asked me to submit a patch "in-reply the previous version" in <20150922091757.GZ3383@phenom.ffwll.local> and I adhered to that request also when sending a new version of an entire series. In that case I'll *not* submit in-reply-to in the future, got that. Best regards, Lukas _______________________________________________ Intel-gfx mailing list Intel-gfx@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/intel-gfx
