All of lore.kernel.org
 help / color / mirror / Atom feed
From: George Dunlap <george.dunlap@cloud.com>
To: Julien Grall <julien@xen.org>
Cc: xen-devel@lists.xenproject.org, 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>,
	 Stefano Stabellini <sstabellini@kernel.org>,
	Wei Liu <wl@xen.org>
Subject: Re: [PATCH 5/8] docs/process: branching-checklist: Reword the section about Config.mk
Date: Mon, 12 Dec 2022 12:33:45 +0000	[thread overview]
Message-ID: <CA+zSX=b3rA=Jc4Au5DhpZK9HZ484sxdR3GdCD6Gjpx114aiyvg@mail.gmail.com> (raw)
In-Reply-To: <20221212093410.36289-6-julien@xen.org>

[-- Attachment #1: Type: text/plain, Size: 1504 bytes --]

On Mon, Dec 12, 2022 at 9:34 AM Julien Grall <julien@xen.org> wrote:

> From: Julien Grall <jgrall@amazon.com>
>
> Since at least Xen 4.12, the revision for external trees don't contain
> the word "unstable". So explicitely list the *_REVISION variables that
> need to be updated as part of the branching process.
>
> Signed-off-by: Julien Grall <jgrall@amazon.com>
> ---
>  docs/process/branching-checklist.txt | 8 +++-----
>  1 file changed, 3 insertions(+), 5 deletions(-)
>
> diff --git a/docs/process/branching-checklist.txt
> b/docs/process/branching-checklist.txt
> index d1550385c96e..7004f16e8311 100644
> --- a/docs/process/branching-checklist.txt
> +++ b/docs/process/branching-checklist.txt
> @@ -69,11 +69,9 @@ ov=4.0
>      git add versions
>      git commit -m "Branch for $v"
>
> -Ensure references to qemu trees in xen.git's Config.mk are updated.
> -Check this with
> -    grep unstable Config.mk
> -which should produce no output.  Replace as necessary.
> -(There may well be none.)
> +Ensure references to qemu trees and Mini-OS in xen.git's Config.mk are
> updated.
> +The variables are QEMU_UPSTREAM_REVISION, QEMU_TRADITIONAL_REVISION and
> +MINIOS_UPSTREAM_REVISION.
>

One advantage of the previous wording was that it helped you know what the
references *weren't* supposed to look like (although it might have been
more helpful to know what the references *were* supposed to look like).
Would it make sense to add a few words about what they're supposed to look
like?

 -George

[-- Attachment #2: Type: text/html, Size: 2106 bytes --]

  reply	other threads:[~2022-12-12 12: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 ` [PATCH 4/8] docs/process: branching-checklist: Clarify steps to add the branch in osstest Julien Grall
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 [this message]
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='CA+zSX=b3rA=Jc4Au5DhpZK9HZ484sxdR3GdCD6Gjpx114aiyvg@mail.gmail.com' \
    --to=george.dunlap@cloud.com \
    --cc=Henry.Wang@arm.com \
    --cc=andrew.cooper3@citrix.com \
    --cc=george.dunlap@citrix.com \
    --cc=jbeulich@suse.com \
    --cc=jgrall@amazon.com \
    --cc=julien@xen.org \
    --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.