From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1034907AbcIWOgp (ORCPT ); Fri, 23 Sep 2016 10:36:45 -0400 Received: from mga01.intel.com ([192.55.52.88]:13530 "EHLO mga01.intel.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1034884AbcIWOgo (ORCPT ); Fri, 23 Sep 2016 10:36:44 -0400 X-ExtLoop1: 1 X-IronPort-AV: E=Sophos;i="5.30,381,1470726000"; d="scan'208";a="1061018601" Date: Fri, 23 Sep 2016 22:36:37 +0800 From: Ye Xiaolong To: LKML Cc: lkp@01.org, kbuild-all@01.org, Fengguang Wu Subject: [LKP] Tips to append base tree info by git-format-patch Message-ID: <20160923143637.GA11833@yexl-desktop> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.5.21 (2010-09-15) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Hi, Here's a tip for people who've been bothered by messages sent by kbuild bot like below: [auto build test ERROR on net/master] [also build test ERROR on v4.8-rc3 next-20160825] [if your patch is applied to the wrong git tree, please drop us a note to help improve the system] It means that 0day bot applied the patch to net/master which is obtained based on heuristic (0day bot does a guess job based on the MAINTAINERS file in linux src to get the tree/branch ). It can't guarantee 100% accuracy. To avoid false reports which is caused by 0day apply your patches to a wrong tree, we suggest to use the new option --base which is introduced since git 2.9.0 to append the base tree info, here is a example of it: Imagine that on top of the public commit P, you applied well-known (on-flight) patches X, Y and Z from somebody else or yourself, and then built your three-patch series A, B, C, the history would be like: ................................................ ---P---X---Y---Z---A---B---C ................................................ With `git format-patch --base=P -3 C`, where P could be the exact commit sha, or variants e.g. HEAD~6, you can also use --base=auto for convenience, the base tree information block is shown at the end of the first message the command outputs (either the first patch, or the cover letter), like this: ------------ base-commit: P prerequisite-patch-id: X prerequisite-patch-id: Y prerequisite-patch-id: Z ------------ For more information, please refer to: https://git-scm.com/docs/git-format-patch We'll be appreciated if you could use this option if you'd like your patch series to be verified by 0day on a solid base as yours. Feedbacks are welcome! Please drop us a mail if you have any suggestions. Thanks, Xiaolong