-
Notifications
You must be signed in to change notification settings - Fork 22
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Use b4 to generate release notes from PR #1
Open
amir73il
wants to merge
10
commits into
mricon:master
Choose a base branch
from
amir73il:release-notes
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
With "-o -" write mbox with no cover to stdout. Signed-off-by: Amir Goldstein <amir73il@gmail.com>
amir73il
force-pushed
the
release-notes
branch
5 times, most recently
from
March 30, 2022 09:40
0c86a1a
to
5963f7c
Compare
b4 pr cannot auto-discover merge-base on a merged pull request. In order to explode a merged PR into patches mbox, provide the msgid of the PR tracker reply, which contains the merge commit id. Don't try to read msgid's from stdin if provided as argument. Signed-off-by: Amir Goldstein <amir73il@gmail.com>
With add_message(..., needcover=True) try harder to find the cover letter of the message by looking at in-reply-to. Regardless of needcover, always accept cover letter with numbering 0/N but without diffstat, like this one: https://lore.kernel.org/all/20220317053907.164160-1-david@fromorbit.com/ Signed-off-by: Amir Goldstein <amir73il@gmail.com>
nocache was not passed into get_extra_series() by callers and wantvers was passed in as wrong type. Signed-off-by: Amir Goldstein <amir73il@gmail.com>
amir73il
force-pushed
the
release-notes
branch
2 times, most recently
from
March 30, 2022 21:10
b978194
to
809fb12
Compare
amir73il
force-pushed
the
release-notes
branch
4 times, most recently
from
April 10, 2022 14:31
cd05e6e
to
b28ab63
Compare
With get_extra_series([], base_msg=base_msg, direction=0, ...), get the latest revision of series from public-inbox with a match to base_msg subject. This will be used when base_msg refer to a patch in a local mbox where neither the revision nor the date nor author of the local patch is relevant for the search. Signed-off-by: Amir Goldstein <amir73il@gmail.com>
When query starts with an empty msgs list, try to use cached results from previous query of the same base_msg. When base_msg is a git am formatted message without a message id use commit id as cache key. Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Associate patches in patch queue to patch series and for every patch series provide a lore link to latest revision. Can be used to produce release notes draft to add to a pull request: git format-patch <revision range> --stdout | b4 rn -m - To produce release notes before merging a pull request: b4 pr -e -o - <PR msgid> | b4 rn -m - And to produce release notes from a merged pull request: b4 pr -e -o - <PR tracker reply msgid> | b4 rn -m - See tests/linux_rn.sh for examples. Signed-off-by: Amir Goldstein <amir73il@gmail.com>
If output file suffux is .rst, generate release notes in reStructuredText format. Signed-off-by: Amir Goldstein <amir73il@gmail.com>
If any of the messages in the series has references a fstests test name, print the tests in release notes. Signed-off-by: Amir Goldstein <amir73il@gmail.com>
When a patch is found in PR whose subject is not found in public inbox, list the patch is release notes as: - [PATCH ?/?] ... Because we do not know if it is part of a patch series and we have no link to public inbox. Signed-off-by: Amir Goldstein <amir73il@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Example:
$ b4 pr -e -o xfs-5.18.mbx 164817214223.9489.12483808836905609419.pr-tracker-bot@kernel.org
$ b4 rn -m xfs-5.18.mbx 2>/dev/null
Changes in [GIT PULL] xfs: new code for 5.18:
[https://lore.kernel.org/r/20220323164821.GP8224@magnolia]
[PATCH] xfs: add missing cmap->br_state = XFS_EXT_NORM update
[https://lore.kernel.org/r/20220217095542.68085-1-hsiangkao@linux.alibaba.com]
[PATCH RESEND] xfs: don't generate selinux audit messages for capability testing
[https://lore.kernel.org/r/20220301025052.GF117732@magnolia]
[PATCHSET 0/2] xfs: use setattr_copy to set VFS file attributes
[https://lore.kernel.org/r/164685372611.495833.8601145506549093582.stgit@magnolia]
[PATCHSET v3 0/2] xfs: make quota reservations for directory changes
[https://lore.kernel.org/r/164694920783.1119636.13401244964062260779.stgit@magnolia]
[PATCHSET v2 0/2] xfs: constify dotdot global variable
[https://lore.kernel.org/r/164694922267.1119724.17942999738634110525.stgit@magnolia]
[PATCH 0/7 v4] xfs: log recovery fixes
[https://lore.kernel.org/r/20220317053907.164160-1-david@fromorbit.com]