From: Xiaolong Ye <xiaolong.ye@intel.com>
To: git@vger.kernel.org
Cc: fengguang.wu@intel.com, ying.huang@intel.com,
philip.li@intel.com, julie.du@intel.com,
Xiaolong Ye <xiaolong.ye@intel.com>
Subject: [RFC/PATCH 0/1] Add an option to git-format-patch to record base tree info
Date: Mon, 22 Feb 2016 10:58:57 +0800 [thread overview]
Message-ID: <1456109938-8568-1-git-send-email-xiaolong.ye@intel.com> (raw)
Hi,
I am a developer of 0-Day kernel test infrastructure(It is a service and
test framework for automated regression-testing that intercepts linux kernel
development at its early stages [1]), and as proposed by developers in ksummit-discuss,
we have implemented a framework to test all patches sent to LKML, it could help
us to find out potential build/boot/regression errors as early as possible.
In order to test LKML patches on their correct trees, we need to know the
corresponding base tree info, such as git url, branch, base commit id, etc,
currently we did some guess works and it may apply patches to the wrong base
trees, leading to undesirable false positives.
The only clean solution is for the developers to include these base tree info in
their first [PATCH] email, so we propose to add an option "--base-tree-info" to
git-format-patch to record these info in cover letter or the first patch
(put it between the "---" marker line and the actual diff), we believe it would
also be useful for maintainers who use git to manage their projects.
The initial implementation only record the base(parent) commit SHA1 of the
first patch. Here is the example:
1) with cover letter
you could see the commit id at the bottom of the message.
2) without cover letter
Signed-off-by: Xiaolong Ye <xiaolong.ye@intel.com>
---
builtin/log.c | 17 +++++++++++++++++
diff.c | 4 ++++
diff.h | 3 ++-
revision.h | 1 +
4 files changed, 24 insertions(+), 1 deletion(-)
base commit: 0233b800c838ddda41db318ee396320b3c21a560
diff --git a/builtin/log.c b/builtin/log.c
index 0d738d6..49fe8c2 100644
--- a/builtin/log.c
+++ b/builtin/log.c
What do you think? Any review comments about this patch or any suggestions
to us would be greatly appreciated.
[1] https://01.org/lkp/documentation/0-day-test-service
Thanks,
Xiaolong.
Xiaolong Ye (1):
format-patch: add an option to record base tree info
builtin/log.c | 18 ++++++++++++++++++
diff.c | 4 ++++
diff.h | 3 ++-
revision.h | 1 +
4 files changed, 25 insertions(+), 1 deletion(-)
base commit: 0233b800c838ddda41db318ee396320b3c21a560
--
2.7.1.340.gf1cebb4
next reply other threads:[~2016-02-22 3:01 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-22 2:58 Xiaolong Ye [this message]
2016-02-22 2:58 ` [RFC/PATCH 1/1] format-patch: add an option to record base tree info Xiaolong Ye
2016-02-22 4:19 ` Junio C Hamano
2016-02-22 7:30 ` Jacob Keller
2016-02-23 1:47 ` Fengguang Wu
2016-02-23 6:54 ` Junio C Hamano
2016-02-23 9:17 ` Fengguang Wu
2016-02-23 9:23 ` H. Peter Anvin
2016-02-23 9:32 ` Fengguang Wu
2016-02-23 10:32 ` Dan Carpenter
2016-02-23 12:00 ` Fengguang Wu
2016-02-23 13:31 ` Dan Carpenter
2016-02-24 2:55 ` Fengguang Wu
2016-02-24 6:30 ` Junio C Hamano
2016-02-24 7:07 ` Fengguang Wu
2016-02-24 18:34 ` Junio C Hamano
2016-02-23 19:51 ` Junio C Hamano
2016-02-23 20:08 ` Eric W. Biederman
2016-02-23 20:35 ` Junio C Hamano
2016-02-23 20:46 ` H. Peter Anvin
2016-02-23 21:49 ` Eric W. Biederman
2016-02-24 1:40 ` H. Peter Anvin
2016-02-23 22:21 ` Stefan Beller
2016-02-24 10:31 ` Michael J Gruber
2016-02-24 6:19 ` Junio C Hamano
2016-02-24 3:36 ` Fengguang Wu
2016-02-24 3:13 ` Fengguang Wu
2016-02-23 19:56 ` Eric W. Biederman
2016-02-24 2:30 ` Fengguang Wu
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=1456109938-8568-1-git-send-email-xiaolong.ye@intel.com \
--to=xiaolong.ye@intel.com \
--cc=fengguang.wu@intel.com \
--cc=git@vger.kernel.org \
--cc=julie.du@intel.com \
--cc=philip.li@intel.com \
--cc=ying.huang@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).