[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <559CCC9D.8050606@users.sourceforge.net>
Date: Wed, 8 Jul 2015 09:09:17 +0200
From: SF Markus Elfring <elfring@...rs.sourceforge.net>
To: Julian Calaby <julian.calaby@...il.com>
Cc: Frans Klaver <fransklaver@...il.com>,
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 <linux-wireless@...r.kernel.org>,
"devel@...verdev.osuosl.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
> There's a file in the documentation directory of the kernel
> tree describing submitting patches and email client setup.
> Read them both,
I read this information several times.
> do what they say without anything extra.
Do you see any special consequences if a bit of "extra" functionality
is already provided by the Git software for a while?
> Your attempts to "improve" on the system are unnecessary
It seems that my approach does not need improvements for the current
command "git am".
Would a few extensions for the available documentation help to clarify
the situation?
Do items like "commit mail address" and "commit timestamp"
belong together for the data structure "author" by design
in this content management system?
> and annoying people.
I understand that various update suggestions can be surprising.
It is also usual that corresponding acceptance might take
a bit longer than what some contributors would prefer.
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