DPDK website maintenance
 help / color / mirror / Atom feed
From: Thomas Monjalon <thomas@monjalon.net>
To: Lincoln Lavoie <lylavoie@iol.unh.edu>
Cc: web@dpdk.org
Subject: Re: [PATCH] web: updated ci testing information
Date: Fri, 13 Jan 2023 15:05:11 +0100	[thread overview]
Message-ID: <6753024.G0QQBjFxQf@thomas> (raw)
In-Reply-To: <20221215141421.10065-1-lylavoie@iol.unh.edu>

15/12/2022 15:14, Lincoln Lavoie:
> @@ -42,6 +45,8 @@ There are three kinds of inputs to be tested:
>  with [patchwork](//patches.dpdk.org/project/dpdk/list/)
>  - per-commit testing after merges
>  in mainline or dpdk-next- [repositories](//git.dpdk.org/)
> +- per-commit testing of LTS staging commits in the
> +*-staging branches of the [stable repository](//git.dpdk.org/dpdk-stable/)

Instead of adding 4th type (note "there are three kinds of inputs" above),
may I suggest to reword the previous type to include stable repository?

 - per-commit testing after merges
-in mainline or dpdk-next- [repositories](//git.dpdk.org/)
+in mainline, stable or dpdk-next-* [repositories](//git.dpdk.org/)

I think the name of the branch is a detail here.

If you agree I can push with this change.



  reply	other threads:[~2023-01-13 14:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-15 14:14 Lincoln Lavoie
2023-01-13 14:05 ` Thomas Monjalon [this message]
2023-02-27 15:34   ` Thomas Monjalon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=6753024.G0QQBjFxQf@thomas \
    --to=thomas@monjalon.net \
    --cc=lylavoie@iol.unh.edu \
    --cc=web@dpdk.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).