From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/fconfig: update the upstream URL in Config.in
Date: Tue, 26 Nov 2019 16:59:05 +0100 [thread overview]
Message-ID: <20191126165905.1bfb2046@windsurf> (raw)
In-Reply-To: <20191126143352.26682-1-mark@dibsco.co.uk>
On Tue, 26 Nov 2019 14:33:52 +0000
Mark Corbin <mark@dibsco.co.uk> wrote:
> Update the upstream URL in the help text in Config.in. This
> addresses the 'Invalid(Err)' URL status in the package stats
> web page output.
>
> In this case we will use http://sources.buildroot.net/ as no
> real upstream location can be found.
>
> Signed-off-by: Mark Corbin <mark@dibsco.co.uk>
> ---
> package/fconfig/Config.in | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/package/fconfig/Config.in b/package/fconfig/Config.in
> index e7dd58a84a..ee14a2102a 100644
> --- a/package/fconfig/Config.in
> +++ b/package/fconfig/Config.in
> @@ -3,4 +3,4 @@ config BR2_PACKAGE_FCONFIG
> help
> fconfig - get/set RedBoot configuration parameters from Linux.
>
> - http://andrzejekiert.ovh.org/software.html.en
> + http://sources.buildroot.net/fconfig/
I don't think it makes a lot of sense to point to
sources.buildroot.net, I think in such situation, we should just not
have an upstream URL.
Thomas
--
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com
prev parent reply other threads:[~2019-11-26 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-26 14:33 [Buildroot] [PATCH 1/1] package/fconfig: update the upstream URL in Config.in Mark Corbin
2019-11-26 15:59 ` Thomas Petazzoni [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=20191126165905.1bfb2046@windsurf \
--to=thomas.petazzoni@bootlin.com \
--cc=buildroot@busybox.net \
/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.