diff options
| author | Simon Glass <sjg@chromium.org> | 2020-10-29 21:46:36 -0600 |
|---|---|---|
| committer | Simon Glass <sjg@chromium.org> | 2020-11-05 09:11:31 -0700 |
| commit | 8f9ba3ab56c49880fb13fc483493b635f787627c (patch) | |
| tree | b83166cab86194a61fa68b982a31e73309e42a8b /tools/patman/README | |
| parent | dc6df972c9ee2afefd937bee3771865012daccef (diff) | |
| download | u-boot-8f9ba3ab56c49880fb13fc483493b635f787627c.tar.gz | |
patman: Support updating a branch with review tags
It is tedious to add review tags into the local branch and errors can
sometimes be made. Add an option to create a new branch with the review
tags obtained from patchwork.
Signed-off-by: Simon Glass <sjg@chromium.org>
Diffstat (limited to 'tools/patman/README')
| -rw-r--r-- | tools/patman/README | 19 |
1 files changed, 17 insertions, 2 deletions
diff --git a/tools/patman/README b/tools/patman/README index 46b8e251ca..15da6dc33c 100644 --- a/tools/patman/README +++ b/tools/patman/README @@ -11,11 +11,13 @@ This tool is a Python script which: - Runs the patches through checkpatch.pl and its own checks - Optionally emails them out to selected people -It also shows review tags from Patchwork so you can update your local patches. +It also has some Patchwork features: +- shows review tags from Patchwork so you can update your local patches +- pulls these down into a new branch on request It is intended to automate patch creation and make it a less error-prone process. It is useful for U-Boot and Linux work so far, -since it uses the checkpatch.pl script. +since they use the checkpatch.pl script. It is configured almost entirely by tags it finds in your commits. This means that you can work on a number of different branches at @@ -385,6 +387,19 @@ attracted another review each. If the series needs changes, you can update these commits with the new review tag before sending the next version of the series. +To automatically pull into these tags into a new branch, use the -d option: + + patman status -d mtrr4 + +This will create a new 'mtrr4' branch which is the same as your current branch +but has the new review tags in it. The tags are added in alphabetic order and +are placed immediately after any existing ack/review/test/fixes tags, or at the +end. You can check that this worked with: + + patman -b mtrr4 status + +which should show that there are no new responses compared to this new branch. + Example Work Flow ================= |