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

Path	csiph.com!aioe.org!bofh.it!news.nic.it!robomod
From	SF Markus Elfring <elfring@users.sourceforge.net>
Newsgroups	linux.kernel
Subject	Re: Clarification for the use of additional fields in the message body
Date	Tue, 07 Jul 2015 18:20:01 +0200
Message-ID	<pJDLb-7RF-5@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>
X-Original-To	Frans Klaver <fransklaver@gmail.com>
X-Enigmail-Draft-Status	N1110
User-Agent	Mozilla/5.0 (Windows NT 6.1; WOW64; rv:38.0) Gecko/20100101 Thunderbird/38.0.1
MIME-Version	1.0
Content-Type	text/plain; charset=utf-8
Content-Transfer-Encoding	8bit
X-Provags-ID	V03:K0:aNxBYxSLiDQGHobNJDaAR5q1RD51HLe5iYCl44OFe2lkTgUhJV6 /IscYov9ShkEAptfZwrQHp30ToGCHhrtPWevALyKRRyyjytSn8fPvZvq+kyGSJghHUPM8lL 6mlVPCCJh9S6PmfPBvgmUrFEVtv/kHBpp20QTQPZwfxyNhE8iB9dx2UZVF+u+aKskCrL8Uy iNrfJW9242EMcWj4rKFgQ==
X-Ui-Out-Filterresults	notjunk:1;V01:K0:yi0LMV0+KVc=:KARL2m8oo1rsXNVV+/p+tG cVPSzOod6LjSTiAhFodl8pziRZYQD/I4Lr5HYafJz39YaPWFYngz1ZKQlX1BZU3u3Ejy+z797 jka4wdY8qqrLscjNnIIxcmvzVZeDa2dyQ9Qp/bIcaDe11q6dm8+GTyI0lcM8wZ8yTMz32bEz+ gh3h/yORBL1kbs5qDwvni1IG4y0j4q+/sN2997VHdXONPdEs+DArfH4zpRWlQgu91EQN5u+50 X/9XsMQFKQy8btNXFLZalZeRLTuOFfq0jZ68Ax8LNgagvsZagz5/fPYdEqDWxSuvzPDarLI/h wD++b4618BHUZOST+evJ+M6wBDSmxKKt8o2ezYZNj+fYmPMYTg/v/4kiMPVFylsmomMkLZjI9 OUFuL3mU4Q0nPMHAuJq4hPSG1SeEtYCUm36E8yzjowrkFpWhlbxCRA553pExWRaeqvlw33KKb zKwH8UuhuR3xuywFEhjFDaBDIzFRigqV6nJ77i3r1//JM10O7ySaMvvl6qebG4JUoJ4sp8Qyh Yke6Yq/BaUsyNKAqIyqR7HR6JPRER/mD35cnP8VIFv1limcY+twbzHsSAbZMR6GDTtwF30ntg AFZCDVrF9jYgt1mAjZbXh/Aq4M2c4WGqeN084bpVfmZi9V2gC4LpEHZdZce/j2FtaTDvNt+DF 00n7xATzSn83Oj2ZoAbeu+yhJ9lv9EHey/lXxXOj5LVQbVtpVx8xbjqV6bbi4wIeDo3g=
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	31
Organization	linux.* mail to news gateway
X-Original-Cc	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@vger.kernel.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	Tue, 7 Jul 2015 18:15:21 +0200
X-Original-Message-ID	<559BFB19.2080700@users.sourceforge.net>
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>
X-Original-Sender	linux-kernel-owner@vger.kernel.org
Xref	aioe.org linux.kernel:1178697

Show key headers only | View raw

> 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?


> 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?

Regards,
Markus
--
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/

Back to linux.kernel | Previous | Next — Next in thread | Find similar | Unroll thread

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