public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Randall Vasquez" <ran.dall@icloud.com>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] repo/proj/guru:dev commit in: dev-go/staticcheck/
Date: Sat, 30 Jul 2022 21:04:11 +0000 (UTC)	[thread overview]
Message-ID: <1659214998.885a3c48cc0964b4146e2eebf1da85bf6233232d.ran.dall@gentoo> (raw)

commit:     885a3c48cc0964b4146e2eebf1da85bf6233232d
Author:     Randall T. Vasquez <ran.dall <AT> icloud <DOT> com>
AuthorDate: Sat Jul 30 21:03:18 2022 +0000
Commit:     Randall Vasquez <ran.dall <AT> icloud <DOT> com>
CommitDate: Sat Jul 30 21:03:18 2022 +0000
URL:        https://gitweb.gentoo.org/repo/proj/guru.git/commit/?id=885a3c48

dev-go/staticcheck: ammend metadata.xml

Signed-off-by: Randall T. Vasquez <ran.dall <AT> icloud.com>

 dev-go/staticcheck/metadata.xml | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/dev-go/staticcheck/metadata.xml b/dev-go/staticcheck/metadata.xml
index c54adb945..c661a3475 100644
--- a/dev-go/staticcheck/metadata.xml
+++ b/dev-go/staticcheck/metadata.xml
@@ -6,7 +6,7 @@
     <name>Randall Vasquez</name>
   </maintainer>
   <longdescription lang="en">
-  	The advanced Go linter 
+    Staticcheck is a state of the art linter for the Go programming language. Using static analysis, it finds bugs and performance issues, offers simplifications, and enforces style rules.
   </longdescription>
   <upstream>
     <remote-id type="github">dominikh/go-tools</remote-id>


             reply	other threads:[~2022-07-30 21:04 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-30 21:04 Randall Vasquez [this message]
  -- strict thread matches above, loose matches on Subject: below --
2022-07-30 21:01 [gentoo-commits] repo/proj/guru:dev commit in: dev-go/staticcheck/ Randall Vasquez
2022-07-30 16:47 Randall Vasquez

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=1659214998.885a3c48cc0964b4146e2eebf1da85bf6233232d.ran.dall@gentoo \
    --to=ran.dall@icloud.com \
    --cc=gentoo-commits@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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