public inbox for gentoo-commits@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-commits@lists.gentoo.org
Subject: [gentoo-commits] proj/gentoo-syntax:master commit in: plugin/
Date: Wed, 26 Jan 2022 08:28:52 +0000 (UTC)	[thread overview]
Message-ID: <1643185722.3703d611aaf46a9944095b7c9b8670dab9f8d3c5.mgorny@gentoo> (raw)

commit:     3703d611aaf46a9944095b7c9b8670dab9f8d3c5
Author:     Michał Górny <mgorny <AT> gentoo <DOT> org>
AuthorDate: Tue Jan 25 10:46:07 2022 +0000
Commit:     Michał Górny <mgorny <AT> gentoo <DOT> org>
CommitDate: Wed Jan 26 08:28:42 2022 +0000
URL:        https://gitweb.gentoo.org/proj/gentoo-syntax.git/commit/?id=3703d611

newmetadata: Don't add python@ to dev-python/* by default

Signed-off-by: Michał Górny <mgorny <AT> gentoo.org>

 plugin/newmetadata.vim | 2 --
 1 file changed, 2 deletions(-)

diff --git a/plugin/newmetadata.vim b/plugin/newmetadata.vim
index 629815f..356bb8c 100644
--- a/plugin/newmetadata.vim
+++ b/plugin/newmetadata.vim
@@ -59,8 +59,6 @@ fun! <SID>MakeNewMetadata()
             let l:project = "perl"
         elseif l:category ==# "dev-php"
             let l:project = "php-bugs"
-        elseif l:category ==# "dev-python"
-            let l:project = "python"
         elseif l:category ==# "dev-ruby"
             let l:project = "ruby"
         elseif l:category ==# "dev-tex"


             reply	other threads:[~2022-01-26  8:28 UTC|newest]

Thread overview: 76+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-26  8:28 Michał Górny [this message]
  -- strict thread matches above, loose matches on Subject: below --
2023-12-27 15:58 [gentoo-commits] proj/gentoo-syntax:master commit in: plugin/ Michał Górny
2023-11-02 12:58 Michał Górny
2023-06-14 14:25 Michał Górny
2023-06-14 14:25 Michał Górny
2023-06-14 14:25 Michał Górny
2023-06-14 14:25 Michał Górny
2023-06-14 14:25 Michał Górny
2023-06-14 14:25 Michał Górny
2023-03-15  8:29 Michał Górny
2023-03-14 17:39 Michał Górny
2023-03-14 17:39 Michał Górny
2023-02-01  5:03 Michał Górny
2023-01-02 18:43 Michał Górny
2022-12-04 14:47 Michał Górny
2022-07-13  5:26 Michał Górny
2022-05-02 19:06 Michał Górny
2022-05-02 19:06 Michał Górny
2022-02-06 11:59 Michał Górny
2022-02-03  8:36 Michał Górny
2022-02-03  8:36 Michał Górny
2022-02-03  8:36 Michał Górny
2022-02-03  8:36 Michał Górny
2022-01-26  8:28 Michał Górny
2022-01-26  8:28 Michał Górny
2021-12-10 11:41 Vadim Misbakh-Soloviov
2021-12-10 11:41 Vadim Misbakh-Soloviov
2021-12-08 22:40 Michał Górny
2021-11-06 11:05 Michał Górny
2021-09-11 14:02 Mike Gilbert
2021-08-28 11:20 Michał Górny
2021-08-28 11:02 Michał Górny
2021-07-16 18:36 Michał Górny
2021-07-16 15:30 Michał Górny
2021-07-16 15:30 Michał Górny
2020-10-07 10:07 Michał Górny
2020-06-05  5:28 Michał Górny
2020-06-04  6:02 Michał Górny
2020-03-08 13:24 Michał Górny
2019-12-13 18:29 Mikle Kolyada
2019-12-13 18:27 Mikle Kolyada
2019-11-27  8:16 Michał Górny
2019-08-17  6:52 Michał Górny
2019-06-09 17:35 Michał Górny
2018-09-16 17:17 Michał Górny
2018-08-27 19:52 James Le Cuirot
2018-08-20 20:47 Michał Górny
2018-08-14 14:13 Michał Górny
2018-08-14 14:13 Michał Górny
2018-08-14 13:58 Michał Górny
2018-08-14 13:55 Michał Górny
2017-02-25 16:09 Mike Gilbert
2017-02-25 16:06 Mike Gilbert
2017-02-25 16:03 Mike Gilbert
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-03-05 23:35 Tim Harder
2016-02-01 23:42 Tim Harder
2015-08-10 15:25 Mike Gilbert
2014-11-02  0:28 Tim Harder
2013-06-18 22:36 Tim Harder
2013-06-18 22:36 Tim Harder
2013-02-05  1:25 Tim Harder
2013-01-24 20:00 Tim Harder
2013-01-23 22:53 Tim Harder

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=1643185722.3703d611aaf46a9944095b7c9b8670dab9f8d3c5.mgorny@gentoo \
    --to=mgorny@gentoo.org \
    --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