From: Aravind Machiry <machiry-kGDSB/vTt4g@public.gmane.org>
To: kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: A Quick Survey on a Patch Propagation Tool
Date: Tue, 19 Sep 2017 13:05:06 -0700 [thread overview]
Message-ID: <CANozA0hgsRh=r63fKjs-2T13c9V6eQZS-LQ0d_ZdVCBXQvH8BQ@mail.gmail.com> (raw)
Hi Developer and maintainers,
We (researchers for UC Santa Barbara) are developing a tool that will
help in propagating patches.
Please, It would be great if you can fill a 2-question anonymous
survey: https://goo.gl/forms/5cBSx4axKmc8BEtA3
Would you be interested in a tool, which identifies patches that could
be imported with a minimal or rather no testing?
E.g. Security patches, you can import security patches as they usually
do not affect the functionality.
This tool would use only old source file and the new source file!! No
commit messages, no build setup, nothing!!
Something like: git saferebase?
We actually used the tool on the Linux Main Line repository and it did
identify several (60%) patches which are safe to port or do not affect
the functionality.
This tool could be used to import patches from the main source branch
to your branch without worrying about testing them.
You can also use this tool as a patch monitor, which monitors all
commits to a repository and inform you about patches that do not
affect the functionality or otherwise safe patches.
Note that: This tool is supposed to *help* an expert not to *replace* one.
Thank You,
Aravind
reply other threads:[~2017-09-19 20:05 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='CANozA0hgsRh=r63fKjs-2T13c9V6eQZS-LQ0d_ZdVCBXQvH8BQ@mail.gmail.com' \
--to=machiry-kgdsb/vtt4g@public.gmane.org \
--cc=kernel-testers-u79uwXL29TY76Z2rM5mHXA@public.gmane.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).