All of lore.kernel.org
 help / color / mirror / Atom feed
From: Thomas Petazzoni <thomas.petazzoni@bootlin.com>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/tcping: update the upstream URL in Config.in
Date: Wed, 18 Dec 2019 23:26:27 +0100	[thread overview]
Message-ID: <20191218232627.5d977ac3@windsurf> (raw)
In-Reply-To: <20191218132736.8052-1-mark@dibsco.co.uk>

Hello Mark,

On Wed, 18 Dec 2019 13:27:36 +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.
> 
> Signed-off-by: Mark Corbin <mark@dibsco.co.uk>
> ---
>  package/tcping/Config.in | 2 +-
>  1 file changed, 1 insertion(+), 1 deletion(-)
> 
> diff --git a/package/tcping/Config.in b/package/tcping/Config.in
> index e72df096c3..241561ce10 100644
> --- a/package/tcping/Config.in
> +++ b/package/tcping/Config.in
> @@ -11,4 +11,4 @@ config BR2_PACKAGE_TCPING
>  	  desired port is reachable and then start connection
>  	  establishment.
>  
> -	  http://linuxco.de/tcping/tcping.html
> +	  https://web.archive.org/web/20171102193822/linuxco.de/tcping/tcping.html

The tcping we have in Buildroot, in version 1.3.5 is from Marc
Kirchner, and he now has a Github at
https://github.com/mkirchner/tcping, where he has both the 1.3.5 and
even a newer 1.3.6 release.

So it seems like the best course of action for this package is to
switch to using this Github repository as the upstream (and of course
not just update Config.in, but also the .mk file and the version).

Thanks!

Thomas
-- 
Thomas Petazzoni, CTO, Bootlin
Embedded Linux and Kernel engineering
https://bootlin.com

      reply	other threads:[~2019-12-18 22:26 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-12-18 13:27 [Buildroot] [PATCH 1/1] package/tcping: update the upstream URL in Config.in Mark Corbin
2019-12-18 22:26 ` 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=20191218232627.5d977ac3@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.