[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Date: Tue, 7 Jul 2015 13:53:58 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Frans Klaver <fransklaver@...il.com>
Cc: Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
Chris Park <chris.park@...el.com>,
Dean Lee <dean.lee@...el.com>,
Johnny Kim <johnny.kim@...el.com>,
Rachel Kim <rachel.kim@...el.com>,
linux-wireless@...r.kernel.org, devel@...verdev.osuosl.org,
Julia Lawall <julia.lawall@...6.fr>,
kernel-janitors@...r.kernel.org,
LKML <linux-kernel@...r.kernel.org>
Subject: Re: Clarification for the use of additional fields in the message
body
> 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
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists