From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1754306AbbGGHzR (ORCPT ); Tue, 7 Jul 2015 03:55:17 -0400 Received: from mout.web.de ([212.227.17.11]:53144 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751041AbbGGHzL (ORCPT ); Tue, 7 Jul 2015 03:55:11 -0400 Subject: Re: Clarification for the use of additional fields in the message body To: Frans Klaver References: <530CD2C4.4050903@users.sourceforge.net> <530CF8FF.8080600@users.sourceforge.net> <530DD06F.4090703@users.sourceforge.net> <5317A59D.4@users.sourceforge.net> <558EB32E.6090003@users.sourceforge.net> <558EB4DE.3080406@users.sourceforge.net> <20150707023103.GA22043@kroah.com> <559B6FF8.9010704@users.sourceforge.net> Cc: Greg Kroah-Hartman , Chris Park , Dean Lee , Johnny Kim , Rachel Kim , linux-wireless@vger.kernel.org, devel@driverdev.osuosl.org, Julia Lawall , kernel-janitors@vger.kernel.org, LKML From: SF Markus Elfring X-Enigmail-Draft-Status: N1110 Message-ID: <559B85CD.6040200@users.sourceforge.net> Date: Tue, 7 Jul 2015 09:54:53 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:38.0) Gecko/20100101 Thunderbird/38.0.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Provags-ID: V03:K0:6XrrM+jRCX8inEFr0Z0BXAr9O0yvPYEAR4AexhK32dM4rD0ykSt +HmdAMWnXruzQ4ctDUr0efNNz4KKghird/VY/O+nG6KXacz1qN+lklOsAjeQVD8upgA8OQT JBXoCkDAOOa5KO3owzPzsi/VUv/kKhCzT9Rm8TrjG07LSqxJuCjJjeexPtwZPTK3ru+LCa2 xN+T99+hPCsRp7zlQnnYw== X-UI-Out-Filterresults: notjunk:1;V01:K0:moqr/4ls6YA=:daaMc/iHw345OIDzyfTyJK 4tQMPLVdBD1RpUHJsQ94MippCva4YpKZLc9mRRmzMffiu6RKvVqwADyS+n/2vUXHDpIi4Iei/ KRFN4r2oAeO0VqEwMP1pDq16JrDiwijLfbgkQTJZI40VB5VehXCFUzrzt6ZiqXISE7Fdl7mXl sGtWXyjOD1bJ10x77honDl4PeLgJdqridu/RRSE8Tls2EO9Gpg+z71ygC/HiBZJghoYjJ6zCb fqTGfuEQFPOek8bAvucHIQZYFh3subaQm3utbVcPWIe/xVUn684MPL5VzJ8sfZ8+BH6bSI8+l CkHrtitGPd2jPRsCT61CKYkxIDUVF9iI7CSsC1JcvSikBtPDKRxNwkkoH8y0zfwLH9yvzfjju 8MaVO6bEz4G7Hh4AdVr+1d7Fh9JFjE1fmHiBfWK5NvLtldjvO0c47eMcPbnJWqKSZyzGwFQWX 6/iFG0SUrlXSpE9ChISI0L00zjU+RDegTAzqwxqBCUlnWzYnzKm6YhtvvhY560K5SS/sOAvW3 Aryk5AZxVxTAkqDcCVGYLmzkB9ydk1vdVddYnKmZLbqfK7g2YwyCHRCGf7Mtb5NMup+ZLXT7p xxPr6fvXYdz9lfqWZ7HI/EWPXXLY1WRPuE7ZMG0DFHpacieCLAw5NJPQXyrGsIxuFpAK4tegp tkmHedbqJtngmqJ6dvQdGg9onaHhKouaa/J3y9XRWYqN9IxNiN3ZBbUSdGPiKZAgnQkg= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > The date, as far as I know, is ignored. It is the commit date, > not the authoring date, and once your patch is applied by a maintainer > (i.e. committed), the date gets reset anyway. Thanks for your feedback. > No need to try and preserve it. I find that it might occasionally help to share and keep the record on timestamps about the evolution for an original update suggestion. Regards, Markus