public inbox for binutils@sourceware.org
 help / color / mirror / Atom feed
From: Christophe Lyon <christophe.lyon@linaro.org>
To: "Carlos O'Donell" <carlos@redhat.com>
Cc: gcc-patches@sourceware.org, jakub@redhat.com, rguenther@suse.de,
	 gerald@pfeifer.com, Nick Clifton <nickc@redhat.com>,
	binutils@sourceware.org,
	 Thiago Bauermann <thiago.bauermann@linaro.org>
Subject: Re: [PATCH] wwwdocs: contribute.html: Update consensus on patch content.
Date: Fri, 26 Apr 2024 11:45:21 +0200	[thread overview]
Message-ID: <CAPS5khaMH2z-FgM-aePzksijObn7C7P2ivRkeAjqUWcF=-iSqg@mail.gmail.com> (raw)
In-Reply-To: <CAPS5khbO2UUF1s5qL6b1YXv7KhMgu_t6BaO6P55LOtkjF8tTKQ@mail.gmail.com>

On Fri, 26 Apr 2024 at 10:25, Christophe Lyon
<christophe.lyon@linaro.org> wrote:
>
> On Thu, 25 Apr 2024 at 17:44, Carlos O'Donell <carlos@redhat.com> wrote:
> >
> > Discussion is here:
> > https://inbox.sourceware.org/gcc/CAPS5khZeWkAD=V8ka9g5eECDNK3BDHFNZJuMpVC+HeDmkVJMCg@mail.gmail.com/
> >
> > Rough consensus from Jakub Jelinek, Richard Biener and others is
> > that maintainers are for the change.
> >
> > This changes the contribution notes to allow it.
>
> Thank you Carlos for the patch and helping with the discussions!
>
> Christophe
>

And BTW sorry I wasn't able to attend the meeting yesterday, thanks
Thiago for raising the question.

I have a follow-up one: I think the same applies to binutils, but I
don't think any maintainer / contributor expressed an opinion, and
IIUC patch policy for binutils is (lightly) documented at
https://sourceware.org/binutils/wiki/HowToContribute
Maybe Nick can update it? (I don't have such rights)

Thanks,

Christophe

> > ---
> >  htdocs/contribute.html | 5 +++--
> >  1 file changed, 3 insertions(+), 2 deletions(-)
> >
> > diff --git a/htdocs/contribute.html b/htdocs/contribute.html
> > index 7c1ae323..e8137edc 100644
> > --- a/htdocs/contribute.html
> > +++ b/htdocs/contribute.html
> > @@ -195,8 +195,9 @@ of your testing.
> >
> >  <dt>The patch itself</dt>
> >  <dd>
> > -Do not include generated files as part of the patch, just mention
> > -them in the ChangeLog (e.g., "<code>* configure: Regenerate.</code>").
> > +The patch should include everything you are changing (including
> > +regenerated files which should be noted in the ChangeLog e.g.
> > +"<code>* configure: Regenerate.</code>").
> >  </dd>
> >
> >  </dl>
> > --
> > 2.44.0
> >

           reply	other threads:[~2024-04-26  9:45 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <CAPS5khbO2UUF1s5qL6b1YXv7KhMgu_t6BaO6P55LOtkjF8tTKQ@mail.gmail.com>]

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='CAPS5khaMH2z-FgM-aePzksijObn7C7P2ivRkeAjqUWcF=-iSqg@mail.gmail.com' \
    --to=christophe.lyon@linaro.org \
    --cc=binutils@sourceware.org \
    --cc=carlos@redhat.com \
    --cc=gcc-patches@sourceware.org \
    --cc=gerald@pfeifer.com \
    --cc=jakub@redhat.com \
    --cc=nickc@redhat.com \
    --cc=rguenther@suse.de \
    --cc=thiago.bauermann@linaro.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 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 read-only IMAP folder(s) and NNTP newsgroup(s).