From: Miquel Raynal via buildroot <buildroot@buildroot.org>
To: "Yann E. MORIN" <yann.morin.1998@free.fr>
Cc: buildroot@buildroot.org
Subject: Re: [Buildroot] [PATCH] README: fix reference to submitting-patches
Date: Tue, 22 Nov 2022 11:16:03 +0100 [thread overview]
Message-ID: <20221122111603.03453f8c@xps-13> (raw)
In-Reply-To: <20221121174905.GI2516@scaer>
Hello Yann,
yann.morin.1998@free.fr wrote on Mon, 21 Nov 2022 18:49:05 +0100:
> Miquel, All,
>
> On 2022-11-16 09:43 +0100, Miquel Raynal via buildroot spake thusly:
> > While looking for refreshing my mind about Buildroot contribution
> > guidelines, I actually stumbled upon a 404 error. It seems like the
> > manual URL has slightly evolved since 2016, so fix it.
> >
> > Signed-off-by: Miquel Raynal <miquel.raynal@bootlin.com>
> > ---
> > README | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/README b/README
> > index 008e996f5f..2d33c8ce37 100644
> > --- a/README
> > +++ b/README
> > @@ -23,4 +23,4 @@ buildroot mailing list: buildroot@buildroot.org
> > You can also find us on #buildroot on OFTC IRC.
> >
> > If you would like to contribute patches, please read
> > -https://buildroot.org/manual.html#submitting-patches
>
> For me, this does not return a 404, but does properly redirect to the
> following URL... Maybe a temporary fluke?
>
> Can you please double-check now?
Oh yeah, the redirection seems to work again, you can safely ignore
this, sorry for the noise.
Thanks,
Miquèl
_______________________________________________
buildroot mailing list
buildroot@buildroot.org
https://lists.buildroot.org/mailman/listinfo/buildroot
next prev parent reply other threads:[~2022-11-22 10:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 8:43 [Buildroot] [PATCH] README: fix reference to submitting-patches Miquel Raynal via buildroot
2022-11-21 17:49 ` Yann E. MORIN
2022-11-22 10:16 ` Miquel Raynal via buildroot [this message]
-- strict thread matches above, loose matches on Subject: below --
2022-11-16 8:37 Miquel Raynal via buildroot
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=20221122111603.03453f8c@xps-13 \
--to=buildroot@buildroot.org \
--cc=miquel.raynal@bootlin.com \
--cc=yann.morin.1998@free.fr \
/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