On 17 Apr 2025, at 14:09, David Marchand wrote:

> On Thu, Apr 17, 2025 at 10:07 AM Simon Horman <ho...@ovn.org> wrote:
>>
>> On Wed, Apr 16, 2025 at 11:46:48AM +0100, Simon Horman wrote:
>>> Update some URLs in documentation that are broken to working URLs
>>> to the same information.
>>>
>>> ---
>>> Changes in v2:
>>> - Removed duplicate word "commit" from patch description (David Marchand)
>>> - The make target is "check-docs" (David Marchand)
>>> - Don't break formatting (David Marchand)
>>> - Use mail-archive.com instead of archive.org (Ilya Maximents)
>>> - Collected reviewed-by tag from David Marchand
>>>
>>> ---
>>> Simon Horman (2):
>>>       Documentation: Update links to DPDK documentation.
>>>       Documentation: Use mail-archive.com URLs for openflow-discuss ML 
>>> links.
>>>
>>>  Documentation/topics/design.rst   | 2 +-
>>>  Documentation/topics/dpdk/phy.rst | 4 ++--
>>>  Documentation/topics/porting.rst  | 2 +-
>>>  3 files changed, 4 insertions(+), 4 deletions(-)
>>>
>>> base-commit: 50dfd1ce32dff9e400ab1fdc0ef26f83f5299429
>>
>> Thanks David and Eelco for your review.
>>
>> I have applied this series to main.
>>
>> - Documentation: Use mail-archive.com URLs for openflow-discuss ML links.
>>  https://github.com/openvswitch/ovs/commit/effb2bb286cf
>> - Documentation: Update links to DPDK documentation.
>>  https://github.com/openvswitch/ovs/commit/88ee8ae0542f
>>
>> I was also able to trivially backport the DPDK documentation update to
>> branch-3.5, and the openflow-discuss documentation update all the way back
>> to branch-3.0. However, I am not sure if applying documentation updates of
>> this nature to branch-* is appropriate. I'd appreciate some feedback on
>> that.
>
> It won't hurt to backport those.
> On the other hand, we don't generate documentation for older branches, do we?

We do not generate docs for older branches, only for the latest. So I guess 
only people looking at older branches (on GitHub) might notice. I’d say the 
backports are not mandatory.

_______________________________________________
dev mailing list
d...@openvswitch.org
https://mail.openvswitch.org/mailman/listinfo/ovs-dev

Reply via email to