From mboxrd@z Thu Jan 1 00:00:00 1970 From: Thomas Petazzoni Date: Wed, 17 Feb 2016 21:50:23 +0100 Subject: [Buildroot] [PATCH 4/5] gtest: Upgrade to GitHub HEAD In-Reply-To: <1531197965.3282303.1455733032855.JavaMail.zimbra@datacom.ind.br> References: <1444859483-2268-1-git-send-email-alan@softiron.co.uk> <1444859483-2268-5-git-send-email-alan@softiron.co.uk> <20151014235522.774491e2@free-electrons.com> <561ED08C.5010301@softiron.co.uk> <1629967145.779413.1445282966636.JavaMail.zimbra@datacom.ind.br> <1531197965.3282303.1455733032855.JavaMail.zimbra@datacom.ind.br> Message-ID: <20160217215023.79adbe1c@free-electrons.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: buildroot@busybox.net Hello, On Wed, 17 Feb 2016 16:17:12 -0200 (BRST), Carlos Santos wrote: > Hello Alan, > > I noticed that this patch set is still in "Changes Requested" state. Is there anything I can do to help? You can take over the patch, make the necessary changes and post an updated version of it. If your changes are limited, it is customary to keep the original author as the author of the patch. If your changes are really major and essentially rewrite the whole patch, then you can re-assign the authorship of the patch to you, but keep a reference to the original author in the commit log. It is definitely more than welcome to pick up old patches for which changes were requested, but whose author didn't had the time to implement. Best regards, Thomas -- Thomas Petazzoni, CTO, Free Electrons Embedded Linux, Kernel and Android engineering http://free-electrons.com