From: Corentin Chary <corentin.chary@gmail.com>
To: "Michał Górny" <mgorny@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] RFC: Add new remote-id types in metadata.dtd
Date: Sat, 21 Apr 2012 13:38:26 +0200 [thread overview]
Message-ID: <20120421113826.GA13543@falgoret> (raw)
In-Reply-To: <20120421113226.2edc9b76@pomiocik.lan>
[-- Attachment #1: Type: text/plain, Size: 1843 bytes --]
On Sat, Apr 21, 2012 at 11:32:26AM +0200, Michał Górny wrote:
> On Thu, 19 Apr 2012 21:32:49 +0200
> Corentin Chary <corentin.chary@gmail.com> wrote:
>
> > On Thu, Apr 19, 2012 at 6:54 PM, Michał Górny <mgorny@gentoo.org>
> > wrote:
> > > On Thu, 19 Apr 2012 17:31:11 +0200
> > > Corentin Chary <corentin.chary@gmail.com> wrote:
> > >
> > >> - <!ATTLIST remote-id type
> > >> (freshmeat|sourceforge|sourceforge-jp|cpan|vim|google-code|ctan|pypi|rubyforge|cran)
> > >> #REQUIRED>
> > >> + <!ATTLIST remote-id type
> > >> (freshmeat|sourceforge|sourceforge-jp|cpan|vim|google-code|ctan|pypi|rubyforge|cran|rubygems|github|gitorious|pecl|pear|bitbucket)
> > >> #REQUIRED>
> > >
> > > Wouldn't it be better if we kept them sorted?
> >
> > There were not, so I just appended them, but I can provide another
> > patch sorting them too if preferred.
>
> I'll appreciate if you could do that, along with that cpan-module
> addition, and if noone objects, I'll just commit that.
>
> --
> Best regards,
> Michał Górny
--- a/metadata/dtd/metadata.dtd 2010-03-02 18:52:11.000000000 +0100
+++ b/metadata/dtd/metadata.dtd 2012-04-21 13:09:52.557223402 +0200
@@ -61,7 +61,7 @@
<!ELEMENT bugs-to (#PCDATA)>
<!-- specify a type of package identification tracker -->
<!ELEMENT remote-id (#PCDATA)>
- <!ATTLIST remote-id type (freshmeat|sourceforge|sourceforge-jp|cpan|vim|google-code|ctan|pypi|rubyforge|cran) #REQUIRED>
+ <!ATTLIST remote-id type (bitbucket|cpan|cpan-module|cran|ctan|freshmeat|github|gitorious|google-code|launchpad|pear|pecl|pypi|rubyforge|rubygems|sourceforge|sourceforge-jp|vim) #REQUIRED>
<!-- category/package information for cross-linking in descriptions
and useflag descriptions -->
--
Corentin Chary
http://xf.iksaif.net/
[-- Attachment #2: Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2012-04-21 11:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-19 15:31 [gentoo-dev] RFC: Add new remote-id types in metadata.dtd Corentin Chary
2012-04-19 16:54 ` Michał Górny
2012-04-19 19:32 ` Corentin Chary
2012-04-21 9:32 ` Michał Górny
2012-04-21 11:38 ` Corentin Chary [this message]
2012-04-19 18:08 ` "Paweł Hajdan, Jr."
2012-04-19 18:57 ` Michał Górny
2012-04-19 20:00 ` Robin H. Johnson
2012-04-20 7:37 ` Kent Fredric
2012-04-20 7:46 ` Corentin Chary
2012-04-20 8:26 ` Kent Fredric
2012-04-20 11:21 ` Corentin Chary
2012-04-20 12:39 ` Kent Fredric
2012-04-20 13:34 ` Corentin Chary
2012-04-20 19:35 ` Kent Fredric
2012-04-20 20:33 ` Corentin Chary
2012-04-21 3:33 ` Kent Fredric
2012-04-21 9:18 ` Corentin Chary
2012-05-12 19:43 ` [gentoo-dev] " Torsten Veller
2012-05-17 0:02 ` Kent Fredric
2012-05-18 6:46 ` Corentin Chary
2012-06-02 17:11 ` [gentoo-dev] remote-id cpan-module Torsten Veller
2012-06-13 12:07 ` Corentin Chary
2012-05-17 0:05 ` [gentoo-dev] Re: RFC: Add new remote-id types in metadata.dtd Kent Fredric
2012-05-22 14:16 ` [gentoo-dev] " Michael Weber
2012-06-02 17:30 ` Michael Weber
2012-06-04 8:14 ` Corentin Chary
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=20120421113826.GA13543@falgoret \
--to=corentin.chary@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=mgorny@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