Mirror of the gdb-patches mailing list
 help / color / mirror / Atom feed
From: Rainer Orth <ro@CeBiTec.Uni-Bielefeld.DE>
To: Andrew Burgess <aburgess@redhat.com>
Cc: Hannes Domani <ssbssa@yahoo.de>,  Eli Zaretskii <eliz@gnu.org>,
	"gdb-patches@sourceware.org" <gdb-patches@sourceware.org>
Subject: Re: [PATCH] Fix procfs.c compilation on Solaris
Date: Wed, 19 Aug 2026 19:27:24 +0200	[thread overview]
Message-ID: <yddqzjuja0z.fsf@CeBiTec.Uni-Bielefeld.DE> (raw)
In-Reply-To: <87ik5615mi.fsf@redhat.com> (Andrew Burgess's message of "Wed, 19 Aug 2026 16:39:49 +0100")

Hi Andrew,

>>> > This patch should also go to the gdb-18 branch: I'm not sure if I should
>>> > just commit it or it needs approval.
>>> 
>>> The rule until now was that each bugfix on the release branch needs a
>>> Bugzilla report.
>>
>> AFAIK a bugzilla report is only necessary after the first release on that
>> branch, but a global maintainer has to approve in any case, see:
>> https://sourceware.org/gdb/wiki/PushingToReleaseBranch
>
> This is how I've always understood the rule too.  I'm happy to see this
> pushed to gdb-18-branch if it has not already been done so.
>
> Approved-By: Andrew Burgess <aburgess@redhat.com>

done now.

Thanks.
	Rainer

-- 
-----------------------------------------------------------------------------
Rainer Orth, Center for Biotechnology, Bielefeld University

      reply	other threads:[~2026-08-19 17:27 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-14  9:34 Rainer Orth
2026-08-14 11:33 ` Eli Zaretskii
2026-08-14 11:49   ` Hannes Domani
2026-08-19 15:39     ` Andrew Burgess
2026-08-19 17:27       ` Rainer Orth [this message]

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=yddqzjuja0z.fsf@CeBiTec.Uni-Bielefeld.DE \
    --to=ro@cebitec.uni-bielefeld.de \
    --cc=aburgess@redhat.com \
    --cc=eliz@gnu.org \
    --cc=gdb-patches@sourceware.org \
    --cc=ssbssa@yahoo.de \
    /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