From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S932089AbbGGLyc (ORCPT ); Tue, 7 Jul 2015 07:54:32 -0400 Received: from mout.web.de ([212.227.17.11]:60831 "EHLO mout.web.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1754520AbbGGLyW (ORCPT ); Tue, 7 Jul 2015 07:54:22 -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> <559B85CD.6040200@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: <559BBDD6.7040808@users.sourceforge.net> Date: Tue, 7 Jul 2015 13:53:58 +0200 User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; 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:hwhzqxbQy51xamsoMEeSvBBTqkZYyhlhEOS3LEqHqsMPU/UJenH p9Rrx6RUVcDz7A3vg0JqsbX5fiL/36PSf9diHllcxcCukn9P6nPV5d40RzjGB/3/uu7bP0l Hn4Qj4ngylWHpjUeNCCssW/N7NYpb80xWMXFOa9G/IZZ9Q6ECBkseQaBtcTfvo9Hf/rbOXt HNrHeX7LBsPzAPYbOoDiw== X-UI-Out-Filterresults: notjunk:1;V01:K0:vQPLpC7ioT4=:rFe3H7bN86Ob2zvfpNySvh p4/VqkFVe5+I5Wy9mGhooyxHkUw/S/ELIJKddWzvejg2l1hTjEggOm/JlMt+RcX8aqkIoWSst wmVDMmAFOeFxFpNS20uzb8rLrcfmDhbnNefJa8TFvJ8OipiQSOcaMvFlPxR3b/Vvr63jpqrIb yTzAWOMQ7IyduMOc83v0PafEjLxkobzjjnAND4I+MkDw/WNfpa5KKkF7z+Wq/w+8NfVI8bciK oYuXIwQ8xHfl38fRcSfVtlzLO4uCJoQqmcbVS6iuqqHdGK013QlGpV8ARryPLBk3nZ9sfQn4o F2gf20QvkUCz5k25InFq5GggziZfi6Ph3zRVRaD5Spq35Y1OknY3+oiBmfxuzxqP8xdm3pJd+ O1F4aDaT3HKU0WjBLTZA+HsCNECCndZeisPKRfDiPgEs6mVeaSpPWNCcDafDwboLF72kBGx7z 7Yvb1dKwgsOdMe4KG4Ov4HfjbNROVt57WcahtgIRDns8Fsu+Dn7Mp9fQKZPHfuIHX0i7PSqkj VnHdLlWIbLLnLreQk/yPUssAN9bOVWVFMuPeYLn5cAY0HUlPMNOTkzseOqpB3c6TcVC18Tbnb vPVUM3ZceAxtRuiSBKCvmMADlz87EzbaRttY/5I2kjPaD6z69Micg1w8/RhpjVvq9cVr8enjj 3Vd3PsgRACOfG9TaB7T7HtvMrKId9tQpu/gKonXAIa/ztcQXe/F7dljcNRhioHq9LKEk= Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org > I think that as far as these kernel mailing lists are concerned, > the date of the update suggestion is the date on which you submitted the patch, > rather than the date you originally committed it to your local tree. I imagine that there are committers who would like to keep corresponding software development history a bit more accurate. > If you wish to keep track of this evolution for yourself, or > wish to share it, you're better off stashing it somewhere in a > (public) git repo that you control. Would it be nicer to preserve such data directly also by the usual mail interface? > If you insist on placing the date somewhere, you can also put the date > there if you wish. It'll be ignored by git when applied. This content management tool provides the capability to store the discussed information by the parameters "--author=" and "--date=", doesn't it? Is the environment variable "GIT_AUTHOR_DATE" also interesting occasionally? How often do you take extra care for passing appropriate data there? Regards, Markus