From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <linux-kernel-owner@vger.kernel.org>
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
	id S1758635AbbGHP16 (ORCPT <rfc822;w@1wt.eu>);
	Wed, 8 Jul 2015 11:27:58 -0400
Received: from mout.web.de ([212.227.17.11]:57849 "EHLO mout.web.de"
	rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP
	id S1755863AbbGHP1z (ORCPT <rfc822;linux-kernel@vger.kernel.org>);
	Wed, 8 Jul 2015 11:27:55 -0400
Subject: Re: Clarification for the use of additional fields in the message
 body
To: "Theodore Ts'o" <tytso@mit.edu>, Julian Calaby <julian.calaby@gmail.com>,
        Frans Klaver <fransklaver@gmail.com>,
        Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
        Chris Park <chris.park@atmel.com>, Dean Lee <dean.lee@atmel.com>,
        Johnny Kim <johnny.kim@atmel.com>, Rachel Kim <rachel.kim@atmel.com>,
        linux-wireless <linux-wireless@vger.kernel.org>,
        "devel@driverdev.osuosl.org" <devel@driverdev.osuosl.org>,
        Julia Lawall <julia.lawall@lip6.fr>, kernel-janitors@vger.kernel.org,
        LKML <linux-kernel@vger.kernel.org>
References: <559B85CD.6040200@users.sourceforge.net>
 <CAH6sp9Npqma18pj=ZsxYpCNDCm-AjjXvw61MGKBEKSYvg_LUBg@mail.gmail.com>
 <559BBDD6.7040808@users.sourceforge.net>
 <CAH6sp9O=NgJXOJzQaaA0o_yae+ae1oJa5Kcqmpo-WWBO_xUW+g@mail.gmail.com>
 <559BFB19.2080700@users.sourceforge.net>
 <CAGRGNgXTN8AxBNNfie4KvvErOXm3LUyL_QLLWQ6TN_wJgJkD-A@mail.gmail.com>
 <559CCC9D.8050606@users.sourceforge.net>
 <CAGRGNgWcHxwjx07A45No8vArXR12JGKcfif1Rvi30PQbJs4SGQ@mail.gmail.com>
 <559CED4C.1080402@users.sourceforge.net>
 <CAGRGNgU1SSUw-97aS0nhFObcMpLPdP3ej9WWNVwN77Fd=ws-bQ@mail.gmail.com>
 <20150708150335.GB20551@thunk.org>
From: SF Markus Elfring <elfring@users.sourceforge.net>
X-Enigmail-Draft-Status: N1110
Message-ID: <559D416A.7050601@users.sourceforge.net>
Date: Wed, 8 Jul 2015 17:27:38 +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: <20150708150335.GB20551@thunk.org>
Content-Type: text/plain; charset=windows-1252
Content-Transfer-Encoding: 7bit
X-Provags-ID: V03:K0:yiL0YIFbloZey9TAjzchP4KR7h4CnsUVyXlDNvwnXGSsNetE/DF
 u4nliigk2+zF3wGMBOzeAXF5PlJVxPET7GW38+iBunCZA79HEnCgHCydBspWY2Pfem9Kvcr
 YnLHEMV8QTPUDnUI0GrxfYJTDY8qqkOmYrMa/KNC2l7gy2W9XbR+UF2pDc4eFdsh6h3FBRs
 D9LV0d9pcGu8MGPymqmag==
X-UI-Out-Filterresults: notjunk:1;V01:K0:DIzTKV/pVSo=:ItGnKGa7OrQx+a/8NbH3KG
 2QGj+r5N11M+cyUO5iLf9mg9wBS4DfVr0kYEpR1MUVPmalKK4Y+4RkCtKRDRG0y786zBb/fg6
 ShuOrK5c1AGnvUm8+KX6RfsbuoHOL18oZoOlhvCbNKPa1knexm2XWStdmISj2SZnoDYjwn25f
 PUJHKDZWX7I2FXQxMF6gv5p7i0KimzKcjbrea5N6l3yk6f0btX/OxTsp8Hlab2KYmYaynAqpq
 6ajKl7dsFRIqqWW94Q1AaxDRd0DkiAWW1rpnaDPrTIHPWn6Fthjb1hgzdi8uaIe+Iwop3u8yl
 DTJOJQGFd0Mv7Ks61A5ZNSyNcdiQpuFpIpNZ24DrXgo9HoBAd28LDQGpPGPDYJ1OmcVtJxEoj
 tPYj5otQOq5KeGr0Ndgurb+n9KN51NRoknOFerUPufU5JcHqlab0w0jkuKWQItbNkG1fHU++o
 CkBN00l3urG6EVbsH0wFiqTl/ccHGBYl9pQNHkmFbvebgdEnzZOesDnCz7SsnLW1pvNIr1Fnu
 Bcb+abqTCGoZfa8Ot8mWJ8Kljzh/Puo5+Mr8QAPJeXvGxGX15gyxfQzZ9uLyEWww0GuLBddr9
 aFHK5d3PE1hGsvyK1zEIWLv9NNxL5uYIDeVZKbIg0F199/JhfDylpPgZO6euEG2AE6fLsgsE1
 rg1KGXADt3RMs5zGR2wVBqMUDDCW7ffxoUqYAeNxB90E858KCgs8CSFvOrn76SvnifF8=
Sender: linux-kernel-owner@vger.kernel.org
List-ID: <linux-kernel.vger.kernel.org>
X-Mailing-List: linux-kernel@vger.kernel.org

> Note also that some maintainers have work flow that deliberately smash
> the date (i.e., because they are using a system such as guilt),
> so if you are depending on the submitted timestamp, it's going to
> break on you.

Thanks for your hint.

I am just trying to offer the possibility for the reuse of a more
precise commit timestamp together with an appropriate author mail
address for my update suggestions.
Do you reject any more such message field overrides?

Regards,
Markus