| Age | Commit message (Collapse) | Author |
|---|
|
Make the name a bit more convenient to invoke and document that it can
be set as an alias.
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
Add the b4-wrapper.sh script that allows running
b4 from a git working directory.
Signed-off-by: Geoff Levand <geoff@infradead.org>
|
|
We don't need to strip() patches, because a) it introduces a problem if
the patch has blank lines in it, and b) because it doesn't matter if
there's anything trailing at the end.
We still need better handling for obviously broken patches, but at least
valid ones shouldn't cause problems.
Reported-by: Geoff Levand <geoff@infradead.org>
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
Anyone who wants a convenient wrapper to run things from the git
checkout without installing pip packages can set up a two-liner wrapper
script and put it in their path.
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
No longer need to change version in both places.
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
There are special cases where we have:
cover: [PATCH v3 00/NN] Foo
\- [PATCH 01/NN] Patch 1
- [PATCH 02/NN] Patch 2
While the submitter *should* be setting "v3" in all patches, it's not
uncommon to have that inferred from the cover letter. When cover letter
is properly upthread from the patch that has an inferred v1 revision, we
can check the revision on the cover letter and fix the patch revision to
match.
Reported-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
I should have it simply use the version in b4/__init__.py
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
If attestation is over 30 days older than the patch, then we refuse to
accept it. This can be changed in configuration parameters by setting
'attestation-staleness-days' to a higher/lower value.
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
If one patch in the series fails attestation, show which one it is and
point out which part failed (commit metadata, commit message, or patch
content). At this time, this only works if it's not the *first* patch
that fails attestation, because otherwise we aren't able to locate the
attestation document in the first place. There's no simple solution
here, because otherwise we'd have to hit lore too many times, which
would be murder on large series.
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
Querying signatures without the trailing slash results in an extra 301
hop that is unnecessary.
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
Don't backtrace if there are no commands passed on cmdline.
Reported-by: Jens Axboe <axboe@kernel.dk>
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
- Uses the correct mailing list tools@linux.kernel.org
- Properly handles the Fixes: follow-up trailers
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
We now properly locate and process Fixes: trailers.
Reported-by: Mark Brown <broonie@kernel.org>
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
This should be most of what's needed for the pip release.
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|
|
This is the beginning of a new tool that inherits from get-lore-mbox and
attest-patches.
Signed-off-by: Konstantin Ryabitsev <konstantin@linuxfoundation.org>
|