[llvm] bb5566a - [llvm][docs] Improve usage note on stacked PRs (#138949)

via llvm-commits llvm-commits at lists.llvm.org
Fri May 16 01:02:21 PDT 2025


Author: Paschalis Mpeis
Date: 2025-05-16T09:02:17+01:00
New Revision: bb5566aac2f236d49c74ce3c53b5c832f4d9a22b

URL: https://github.com/llvm/llvm-project/commit/bb5566aac2f236d49c74ce3c53b5c832f4d9a22b
DIFF: https://github.com/llvm/llvm-project/commit/bb5566aac2f236d49c74ce3c53b5c832f4d9a22b.diff

LOG: [llvm][docs] Improve usage note on stacked PRs (#138949)

Added: 
    

Modified: 
    llvm/docs/GitHub.rst

Removed: 
    


################################################################################
diff  --git a/llvm/docs/GitHub.rst b/llvm/docs/GitHub.rst
index de0022e518cc8..31dee0bbb17ba 100644
--- a/llvm/docs/GitHub.rst
+++ b/llvm/docs/GitHub.rst
@@ -292,9 +292,9 @@ Your options are as follows:
    subsequent PRs in a stack. Instead, it will show a combined 
diff  that
    includes all commits from earlier PRs.
 
-   As described in the first option above, in such cases it is the PR author’s
-   responsibility to clearly indicate which commits are relevant to the
-   current PR. For example: “The first N commits are from the base PR.”
+   As described above, it is the PR author’s responsibility to clearly indicate
+   which commits are relevant to the current PR.
+   For example: “The first N commits are from the base PR.”
 
    You can avoid this issue by using user branches directly in the
    ``llvm/llvm-project`` repository.


        


More information about the llvm-commits mailing list