Re: Clarification for the use of additional fields in the message body

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	Julian Calaby <julian.calaby@gmail.com>
Newsgroups	linux.kernel
Subject	Re: Clarification for the use of additional fields in the message body
Date	Wed, 08 Jul 2015 01:50:02 +0200
Message-ID	<pJKMG-3Fu-3@gated-at.bofh.it> (permalink)
References	<mSsDN-4wa-53@gated-at.bofh.it> <mSsDN-4wa-55@gated-at.bofh.it> <mSsDN-4wa-57@gated-at.bofh.it> <mSsDN-4wa-59@gated-at.bofh.it> <mSsDN-4wa-61@gated-at.bofh.it> <mSsDN-4wa-63@gated-at.bofh.it> <mSsDN-4wa-65@gated-at.bofh.it> <mSsDN-4wa-33@gated-at.bofh.it> <pFZhg-8iz-11@gated-at.bofh.it> <pFZqW-8ud-13@gated-at.bofh.it> <pJsmK-KT-19@gated-at.bofh.it> <pJuye-21t-7@gated-at.bofh.it> <pJuRz-27R-3@gated-at.bofh.it> <pJvXk-2KB-25@gated-at.bofh.it> <pJwqm-39V-21@gated-at.bofh.it> <pJzHA-5bl-21@gated-at.bofh.it> <pJBT3-6FZ-13@gated-at.bofh.it> <pJDLb-7RF-5@gated-at.bofh.it>
X-Original-To	SF Markus Elfring <elfring@users.sourceforge.net>
Dkim-Signature	v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc:content-type:content-transfer-encoding; bh=PMSzgk8MwOl8NKVWy8VRYAnRyYmZDQUPqgouuHTQfY8=; b=LNlzLBy9xdD5P+6xrfVvf5Nj/69Ubrihxjl7IhxCNDdT253KKlf4V/NvdAPHOKHkS2 DOmZPamR+cY1eQZYQoS8p8MbMmznQ3OL8U3AI0j0NwFUqqZrfEYiYkWQ0lWS7S8pCx6C 1DRx37VwVAhUqY8R7cFi6hmFQjxbMK4GmrZyW6oRTaWPU2iWpss2e60ySvco+kg3gPA+ FFI/XLddScK4pVnXCtSLHtLYoMntvZTN05+D4wrYeCAb+9h03JWRU0S7JMpCmCdTB93P HmER9mYFF1DcmQJdy8pAVlPE0XF/fiX/oV9/4nDEd6HvlPbnAtTMtkcDTqJuf000Mm46 lY0A==
X-Received	by 10.107.13.201 with SMTP id 192mr11539584ion.70.1436312616606; Tue, 07 Jul 2015 16:43:36 -0700 (PDT)
MIME-Version	1.0
Content-Type	text/plain; charset=UTF-8
Content-Transfer-Encoding	8BIT
Sender	robomod@news.nic.it
List-ID	<linux-kernel.vger.kernel.org>
X-Mailing-List	linux-kernel@vger.kernel.org
Approved	robomod@news.nic.it
Lines	54
Organization	linux.* mail to news gateway
X-Original-Cc	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>
X-Original-Date	Wed, 8 Jul 2015 09:43:17 +1000
X-Original-Message-ID	<CAGRGNgXTN8AxBNNfie4KvvErOXm3LUyL_QLLWQ6TN_wJgJkD-A@mail.gmail.com>
X-Original-References	<alpine.DEB.2.10.1402251014170.2080@hadrien> <530CD2C4.4050903@users.sourceforge.net> <alpine.DEB.2.10.1402251840450.7035@hadrien> <530CF8FF.8080600@users.sourceforge.net> <alpine.DEB.2.02.1402252117150.2047@localhost6.localdomain6> <530DD06F.4090703@users.sourceforge.net> <alpine.DEB.2.02.1402262129250.2221@localhost6.localdomain6> <5317A59D.4@users.sourceforge.net> <558EB32E.6090003@users.sourceforge.net> <558EB4DE.3080406@users.sourceforge.net> <20150707023103.GA22043@kroah.com> <559B6FF8.9010704@users.sourceforge.net> <CAH6sp9Nn7LKdqT9E0bykY8jpEc-Ugxn8wby5yLcW+nsx=yG3NQ@mail.gmail.com> <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>
X-Original-Sender	linux-kernel-owner@vger.kernel.org
Xref	aioe.org linux.kernel:1179164

Show key headers only | View raw

Hi Markus,

On Wed, Jul 8, 2015 at 2:15 AM, SF Markus Elfring
<elfring@users.sourceforge.net> wrote:
>> I can't remember ever changing or explicitly preserving the commit date.
>> I don't think I care enough.
>
> Would any more software developers and maintainers like to share
> their experiences around such details?
>
> When do commit timestamps become relevant as a documentation item
> for contribution authorship?

They are never relevant.

"When" a commit happened is never relevant except in relation to other
things, at which point the actual date and time is almost completely
irrelevant.

Just submit your patches using git-format-patch or git-send-email and
friends. There's a file in the documentation directory of the kernel
tree describing submitting patches and email client setup. Read them
both, do what they say without anything extra.

>> Remembering the author separately from the committer is something
>> git does by design anyway.
>
> Do you usually just reuse a procedure from a well-known command
> for which a description is provided like the following?
> http://git-scm.com/docs/git-am
> '…
> "From: " and "Subject: " lines starting the body override
> the respective commit author name and title values
> taken from the headers.
> …'
>
> Will further fields be eventually mentioned there?

Why? Just do what is described in SubmittingPatches. Your attempts to
"improve" on the system are unnecessary and annoying people. The
instructions there are the recommended way to do things for a reason.

Thanks,

-- 
Julian Calaby

Email: julian.calaby@gmail.com
Profile: http://www.google.com/profiles/julian.calaby/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Thread

Re: Clarification for the use of additional fields in the message  body SF Markus Elfring <elfring@users.sourceforge.net> - 2015-07-07 18:20 +0200
  Re: Clarification for the use of additional fields in the message body Julian Calaby <julian.calaby@gmail.com> - 2015-07-08 01:50 +0200
    Re: Clarification for the use of additional fields in the message  body SF Markus Elfring <elfring@users.sourceforge.net> - 2015-07-08 15:50 +0200

csiph-web