| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
| |
If the author of a patch series provides a base-commit tag, extract and store the hash.
|
| |
|
|
|
|
|
|
|
|
|
| |
On LKML, users sometimes reply to a patch series while keeping the
original title. At the same time, sometimes new series are sent as a
reply to the previous versions. It all confuses the lore archive
parsing logic.
When reading the archive, remember if the patch were present. If not,
mark the series as corrupted and thus prevent is appearance in
syz-cluster.
|
| |
|
|
|
| |
Wrapping the email.Email object will let us add lore-specific fields to
it at a later point.
|
| |
|
|
|
| |
Sometimes the patch series directly hint at the kernel tree they should
be applied to. Extract and remember this information.
|
| |
|
|
|
| |
Refactor the code to make it more reusable.
Add a method to extract specifically the list of new patch series.
|
| | |
|
| |
|
|
|
|
| |
Patches are not always spelled upper case. Also, looking for just PATCH
may lead to false positives, so first put the subject to lower case and
then look for the "[patch" substring.
|
| |
|
|
|
|
| |
DiscussionReport are the discussions started by syzbot.
All other discussions that Cc syzbot or mention its bugs are
DiscussionMention.
|
| |
|
|
|
|
|
|
|
|
|
| |
Now that too much logic seems to be duplicated in tools/syz-lore and
dahsboard/app/discussion.go, it's time to refactor the code.
Factor out the code that decides whether an incoming email message
should start a new thread or be appended to the previous one.
Restructure pkg/email/lore so that email processing matches the
one-by-one approach of reporting_email.go.
|
| |
|
|
| |
Adjust tests.
|
|
|
We need to
1) Query raw messages from an LKML git archive.
2) Group raw messages into threads.
|
