From 19020d3cb3655928529bda9294aa4e51a5149eef Mon Sep 17 00:00:00 2001
From: Michael Kozono <mkozono@gmail.com>
Date: Fri, 8 Jun 2018 18:00:51 +0000
Subject: [PATCH] Remove unnecessary and broken example

The example provided was broken because it mistakes
a bug for a regression. It is not needed for clarity
anyway. The milestone part is no longer relevant as
well.
---
 PROCESS.md | 6 +-----
 1 file changed, 1 insertion(+), 5 deletions(-)

diff --git a/PROCESS.md b/PROCESS.md
index 7438df8014bb0..958bc7b9edcac 100644
--- a/PROCESS.md
+++ b/PROCESS.md
@@ -185,11 +185,7 @@ next patch release.
 
 If a merge request is to be picked into more than one release it will need one
 `Pick into X.Y` label per release where the merge request should be back-ported
-to.
-
-For example, if the current patch release is `10.1.1` and a regression fix needs
-to be backported down to the `9.5` release, you will need to assign it the
-`10.1` milestone and the following labels:
+to. For example:
 
 - `Pick into 10.1`
 - `Pick into 10.0`
-- 
GitLab