All of lore.kernel.org
 help / color / mirror / Atom feed
From: Julien Grall <julien@xen.org>
To: xen-devel@lists.xenproject.org
Cc: Henry.Wang@arm.com, Julien Grall <jgrall@amazon.com>,
	Andrew Cooper <andrew.cooper3@citrix.com>,
	George Dunlap <george.dunlap@citrix.com>,
	Jan Beulich <jbeulich@suse.com>, Julien Grall <julien@xen.org>,
	Stefano Stabellini <sstabellini@kernel.org>, Wei Liu <wl@xen.org>
Subject: [PATCH 4/8] docs/process: branching-checklist: Clarify steps to add the branch in osstest
Date: Mon, 12 Dec 2022 09:34:06 +0000	[thread overview]
Message-ID: <20221212093410.36289-5-julien@xen.org> (raw)
In-Reply-To: <20221212093410.36289-1-julien@xen.org>

From: Julien Grall <jgrall@amazon.com>

The steps to add the new branch in osstest doesn't mention the change
should be committed.

Update the steps to clarify that. Take the opportunity to switch to
use $v instead hardcoded version.

Signed-off-by: Julien Grall <jgrall@amazon.com>
---
 docs/process/branching-checklist.txt | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/docs/process/branching-checklist.txt b/docs/process/branching-checklist.txt
index a98f6559ab1a..d1550385c96e 100644
--- a/docs/process/branching-checklist.txt
+++ b/docs/process/branching-checklist.txt
@@ -49,7 +49,9 @@ ov=4.0
     OSSTEST_CONFIG=production-config-cambridge ./mg-branch-setup qemu-upstream-$v-testing bisect
 
 * add branch to osstest
-    ie add both eg qemu-upstream-4.2-testing and xen-4.2-testing to BRANCHES in cr-for-branches
+    Add both qemu-upstream-$v-testing and xen-$v-testing to BRANCHES in cr-for-branches
+    git add -p
+    git commit -m "cr-for-branches: Add Xen and QEMU $v branch"
 
 * add to patchbot
     on xenbits
-- 
2.38.1



  parent reply	other threads:[~2022-12-12  9:34 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-12  9:34 [PATCH 0/8] docs/process: branching-checklist: Update it Julien Grall
2022-12-12  9:34 ` [PATCH 1/8] docs/process: branching-checklist: Use consistent indentation Julien Grall
2022-12-12 11:52   ` George Dunlap
2022-12-12  9:34 ` [PATCH 2/8] docs/process: branching-checklist: Remove reference to qemu-ijw.git Julien Grall
2022-12-12 12:10   ` George Dunlap
2022-12-12 14:46   ` Ian Jackson
2022-12-12  9:34 ` [PATCH 3/8] docs/process: branching-checklist: Remove reference to root Julien Grall
2022-12-12 12:11   ` George Dunlap
2022-12-12  9:34 ` Julien Grall [this message]
2022-12-12  9:34 ` [PATCH 5/8] docs/process: branching-checklist: Reword the section about Config.mk Julien Grall
2022-12-12 12:33   ` George Dunlap
2023-02-09 16:59     ` Julien Grall
2022-12-12  9:34 ` [PATCH 6/8] docs/process: branching-checklist: Remove section about the cambridge colo Julien Grall
2022-12-12 12:34   ` George Dunlap
2022-12-12  9:34 ` [PATCH 7/8] docs/proces: branching-checklist: Update the section "add to patchbot" Julien Grall
2022-12-12 12:35   ` George Dunlap
2022-12-12  9:34 ` [PATCH 8/8] docs/process: branching-checklist: Add a list of accounts at the beginning Julien Grall
2022-12-12  9:49 ` [PATCH 0/8] docs/process: branching-checklist: Update it Henry Wang
2022-12-12  9:56   ` Jan Beulich
2023-02-09 17:24   ` Julien Grall

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=20221212093410.36289-5-julien@xen.org \
    --to=julien@xen.org \
    --cc=Henry.Wang@arm.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgrall@amazon.com \
    --cc=sstabellini@kernel.org \
    --cc=wl@xen.org \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.