diff options
| author | Tom Rini <trini@konsulko.com> | 2024-08-26 11:01:40 -0600 |
|---|---|---|
| committer | Tom Rini <trini@konsulko.com> | 2024-09-16 14:33:41 -0600 |
| commit | 640582c72bec7c6336b8be1147a76aa9ac7a0078 (patch) | |
| tree | 86c1037fbfdc517b2f587ef08aa7cfa91ba53c80 /doc/develop | |
| parent | a7b83ade98e0f567c82d168022e12d3ebef1f318 (diff) | |
| download | u-boot-640582c72bec7c6336b8be1147a76aa9ac7a0078.tar.gz u-boot-640582c72bec7c6336b8be1147a76aa9ac7a0078.tar.bz2 u-boot-640582c72bec7c6336b8be1147a76aa9ac7a0078.zip | |
doc/develop/sending_patches.rst: Reword where our git tree is slightly
We shouldn't have had the link to our git tree be contained within "``"
as that meant that it did not work as a link, so remove those. And
rather than make this a link plus text, keep this as a link within the
text for overall clarity.
Suggested-by: Quentin Schulz <quentin.schulz@cherry.de>
Reviewed-by: Neil Armstrong <neil.armstrong@linaro.org>
Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
Signed-off-by: Tom Rini <trini@konsulko.com>
Diffstat (limited to 'doc/develop')
| -rw-r--r-- | doc/develop/sending_patches.rst | 9 |
1 files changed, 4 insertions, 5 deletions
diff --git a/doc/develop/sending_patches.rst b/doc/develop/sending_patches.rst index 9308f428bb..e22b5e3e24 100644 --- a/doc/develop/sending_patches.rst +++ b/doc/develop/sending_patches.rst @@ -76,11 +76,10 @@ General Patch Submission Rules compression, no attachments. Just plain text. The best way to generate patches is by using the ``git format-patch`` command. For a patch that is fixing a bug or regression of some sort, please use the ``master`` branch of - the mainline U-Boot git repository - (``https://source.denx.de/u-boot/u-boot.git``) as reference. For new - features, if the ``next`` branch has been opened (which happens with the - release of ``-rc2``) that branch should be used, otherwise ``master`` is - acceptable. + the mainline U-Boot git repository located at + https://source.denx.de/u-boot/u-boot.git as reference. For new features, if + the ``next`` branch has been opened (which happens with the release of + ``-rc2``) that branch should be used, otherwise ``master`` is acceptable. * Make sure that your mailer does not mangle the patch by automatic changes like wrapping of longer lines etc. |