qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Philippe Mathieu-Daudé" <philmd@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>, qemu-devel@nongnu.org
Cc: stefanha@redhat.com
Subject: Re: [RFC PATCH] .gitpublish: use origin/master as default base
Date: Mon, 29 Sep 2025 16:39:32 +0200	[thread overview]
Message-ID: <b726ecb9-b93c-43ce-9bef-7e18451885a4@linaro.org> (raw)
In-Reply-To: <20250929134348.1589790-1-alex.bennee@linaro.org>

On 29/9/25 15:43, Alex Bennée wrote:
> This is very much the result of my recent fat finger but I think it's
> safer to assume that origin/master points to a recent commit (or at
> least a commit a given branch is based on) than master.
> 
> Signed-off-by: Alex Bennée <alex.bennee@linaro.org>
> ---
>   .gitpublish | 16 ++++++++--------
>   1 file changed, 8 insertions(+), 8 deletions(-)
> 
> diff --git a/.gitpublish b/.gitpublish
> index a13f8c7c0ec..a3adb21ffa1 100644
> --- a/.gitpublish
> +++ b/.gitpublish
> @@ -4,48 +4,48 @@
>   # See https://github.com/stefanha/git-publish for more information
>   #
>   [gitpublishprofile "default"]
> -base = master
> +base = origin/master

Any key to specify the remote? (not everybody have mainstream tracked
as origin).

>   to = qemu-devel@nongnu.org
>   cccmd = scripts/get_maintainer.pl --noroles --norolestats --nogit --nogit-fallback 2>/dev/null
>   
>   [gitpublishprofile "rfc"]
> -base = master
> +base = origin/master
>   prefix = RFC PATCH
>   to = qemu-devel@nongnu.org
>   cccmd = scripts/get_maintainer.pl --noroles --norolestats --nogit --nogit-fallback 2>/dev/null
>   
>   [gitpublishprofile "stable"]
> -base = master
> +base = origin/master
>   to = qemu-devel@nongnu.org
>   cc = qemu-stable@nongnu.org
>   cccmd = scripts/get_maintainer.pl --noroles --norolestats --nogit --nogit-fallback 2>/dev/null
>   
>   [gitpublishprofile "trivial"]
> -base = master
> +base = origin/master
>   to = qemu-devel@nongnu.org
>   cc = qemu-trivial@nongnu.org
>   cccmd = scripts/get_maintainer.pl --noroles --norolestats --nogit --nogit-fallback 2>/dev/null
>   
>   [gitpublishprofile "block"]
> -base = master
> +base = origin/master
>   to = qemu-devel@nongnu.org
>   cc = qemu-block@nongnu.org
>   cccmd = scripts/get_maintainer.pl --noroles --norolestats --nogit --nogit-fallback 2>/dev/null
>   
>   [gitpublishprofile "arm"]
> -base = master
> +base = origin/master
>   to = qemu-devel@nongnu.org
>   cc = qemu-arm@nongnu.org
>   cccmd = scripts/get_maintainer.pl --noroles --norolestats --nogit --nogit-fallback 2>/dev/null
>   
>   [gitpublishprofile "s390"]
> -base = master
> +base = origin/master
>   to = qemu-devel@nongnu.org
>   cc = qemu-s390@nongnu.org
>   cccmd = scripts/get_maintainer.pl --noroles --norolestats --nogit --nogit-fallback 2>/dev/null
>   
>   [gitpublishprofile "ppc"]
> -base = master
> +base = origin/master
>   to = qemu-devel@nongnu.org
>   cc = qemu-ppc@nongnu.org
>   cccmd = scripts/get_maintainer.pl --noroles --norolestats --nogit --nogit-fallback 2>/dev/null



  reply	other threads:[~2025-09-29 14:41 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-29 13:43 [RFC PATCH] .gitpublish: use origin/master as default base Alex Bennée
2025-09-29 14:39 ` Philippe Mathieu-Daudé [this message]
2025-09-29 14:52   ` Alex Bennée
2025-09-29 19:26 ` Stefan Hajnoczi

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=b726ecb9-b93c-43ce-9bef-7e18451885a4@linaro.org \
    --to=philmd@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=qemu-devel@nongnu.org \
    --cc=stefanha@redhat.com \
    /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).