From: Ye Xiaolong <xiaolong.ye@intel.com>
To: LKML <linux-kernel@vger.kernel.org>
Cc: lkp@01.org, kbuild-all@01.org, Fengguang Wu <fengguang.wu@intel.com>
Subject: [LKP] Tips to append base tree info by git-format-patch
Date: Fri, 23 Sep 2016 22:36:37 +0800 [thread overview]
Message-ID: <20160923143637.GA11833@yexl-desktop> (raw)
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
reply other threads:[~2016-09-23 14:36 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20160923143637.GA11833@yexl-desktop \
--to=xiaolong.ye@intel.com \
--cc=fengguang.wu@intel.com \
--cc=kbuild-all@01.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lkp@01.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox