Buildroot Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Corbin <mark@dibsco.co.uk>
To: buildroot@busybox.net
Subject: [Buildroot] [PATCH 1/1] package/fis: add an upstream URL to Config.in
Date: Tue, 26 Nov 2019 20:32:29 +0000	[thread overview]
Message-ID: <1835699.hYYKYNglDJ@laptop> (raw)
In-Reply-To: <20191126210534.168608da@windsurf>

Hello Thomas

On Tuesday, 26 November 2019 20:05:34 GMT Thomas Petazzoni wrote:
> On Tue, 26 Nov 2019 14:43:41 +0000
> 
> Mark Corbin <mark@dibsco.co.uk> wrote:
> > Add an upstream URL to the help text in Config.in. This
> > addresses the 'Missing' URL status in the package stats
> > web page output.
> > 
> > Signed-off-by: Mark Corbin <mark@dibsco.co.uk>
> > ---
> > 
> >  package/fis/Config.in | 2 ++
> >  1 file changed, 2 insertions(+)
> > 
> > diff --git a/package/fis/Config.in b/package/fis/Config.in
> > index c5bfbb82cc..1c6be02978 100644
> > --- a/package/fis/Config.in
> > +++ b/package/fis/Config.in
> > @@ -2,3 +2,5 @@ config BR2_PACKAGE_FIS
> > 
> >  	bool "fis"
> >  	help
> >  	
> >  	  fis - manipulate RedBoot partition table from Linux.
> > 
> > +
> > +	  https://svn.chezphil.org/utils/trunk/
> 
> Just pointing to the source code itself is not that useful. 

At this stage I'm really just trying to clean up some of the noise on the 
package stats page -  http://autobuild.buildroot.org/stats/

I'm quite happy for you to decide whether the links are useful/appropriate.

Regards

Mark

  reply	other threads:[~2019-11-26 20:32 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-26 14:43 [Buildroot] [PATCH 1/1] package/fis: add an upstream URL to Config.in Mark Corbin
2019-11-26 20:05 ` Thomas Petazzoni
2019-11-26 20:32   ` Mark Corbin [this message]
2019-11-26 20:45   ` Peter Korsgaard
2019-11-26 22:47     ` Arnout Vandecappelle
2019-11-26 23:09       ` Peter Korsgaard

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=1835699.hYYKYNglDJ@laptop \
    --to=mark@dibsco.co.uk \
    --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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox