From: Corentin Chary <corentin.chary@gmail.com>
To: gentoo-dev@lists.gentoo.org
Cc: Hans de Graaff <graaff@gentoo.org>
Subject: Re: [gentoo-dev] Re: euscan proof of concept (like debian's uscan)
Date: Wed, 13 Apr 2011 06:47:31 +0000 [thread overview]
Message-ID: <BANLkTimfLTcAZBoEyYcXwBkJpZiH_3eiMA@mail.gmail.com> (raw)
In-Reply-To: <1302425002.25427.7.camel@graaff.xs4all.nl>
On Sun, Apr 10, 2011 at 8:43 AM, Hans de Graaff <graaff@gentoo.org> wrote:
> On Sun, 2011-04-03 at 17:20 +0000, Corentin Chary wrote:
>
>> misc:
>> - automatic bug report
>> - automatic email report for maintainer/herds
>
> I'm not sure if this makes sense. For example, it gets dev-lang/ruby
> wrong, thinking that our old patch files are missing versions. Also, for
> exiftool I only add production releases, so there will almost always be
> newer upstream intermediate releases. My point here is that there are
> often additional considerations in considering new releases, so fully
> automating this is going to be hard. Perhaps a weekly/monthly opt-in
> mail to the herd/maintainer with an overview would be useful?
Better, what about a per-herd/per-maintainer rss feed ?
> The website is nice to have as another source of scanning for updates,
> bookmarked.
The current site won't be updated, I'm working on a new django-based
website that should be up and running next week.
The url will probably be euscan.iksaif.net, but I'll post it here.
--
Corentin Chary
http://xf.iksaif.net
next prev parent reply other threads:[~2011-04-13 6:48 UTC|newest]
Thread overview: 62+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <AANLkTi=LEe+FziC=ong=wym3qi4v9pxxdpEK5wTEz6Dd@mail.gmail.com>
2011-03-21 8:24 ` [gentoo-dev] euscan proof of concept (like debian's uscan) Corentin Chary
2011-03-26 16:35 ` [gentoo-dev] " Christian Faulhammer
2011-03-26 16:41 ` Corentin Chary
2011-09-18 22:27 ` [gentoo-dev] " "Paweł Hajdan, Jr."
2011-09-19 7:35 ` Dirkjan Ochtman
2011-09-19 8:39 ` Corentin Chary
2011-09-19 8:53 ` Michał Górny
2011-09-19 12:51 ` Corentin Chary
2011-09-23 9:55 ` Corentin Chary
2011-04-03 17:20 ` [gentoo-dev] " Corentin Chary
2011-04-10 8:43 ` Hans de Graaff
2011-04-13 6:47 ` Corentin Chary [this message]
2011-04-13 16:23 ` Matthew Summers
2011-04-13 16:58 ` Corentin Chary
2011-04-14 6:49 ` Corentin Chary
2011-04-16 6:29 ` Corentin Chary
2011-04-18 8:26 ` Marijn
2011-04-18 9:05 ` Corentin Chary
2011-04-18 17:22 ` Daniel Pielmeier
2011-04-18 19:14 ` Corentin Chary
2011-04-18 13:32 ` Donnie Berkholz
2011-04-18 13:48 ` Corentin Chary
2011-04-18 19:02 ` Corentin Chary
2011-04-18 19:41 ` Donnie Berkholz
2011-04-18 19:45 ` Donnie Berkholz
2011-04-19 6:19 ` Corentin Chary
2011-04-18 21:08 ` Jorge Manuel B. S. Vicetto
2011-04-19 6:53 ` Corentin Chary
2011-04-19 19:52 ` Tomáš Chvátal
2011-04-20 15:20 ` Corentin Chary
2011-04-27 8:04 ` Corentin Chary
2011-04-27 18:02 ` Tomáš Chvátal
2011-04-28 12:34 ` Corentin Chary
2011-05-02 7:23 ` Corentin Chary
2011-05-05 15:54 ` Corentin Chary
2011-05-06 2:13 ` Patrick Nagel
2011-08-31 13:41 ` Corentin Chary
2011-08-31 16:26 ` Alec Warner
2011-09-01 7:23 ` Alex Legler
2011-09-01 7:44 ` Corentin Chary
2011-09-01 7:49 ` Tomáš Chvátal
2011-09-01 7:55 ` Corentin Chary
2011-09-01 8:05 ` Tomáš Chvátal
2011-09-01 11:47 ` Corentin Chary
2011-09-01 8:31 ` Michał Górny
2011-09-01 9:09 ` Corentin Chary
2011-09-01 14:25 ` Corentin Chary
2011-09-19 19:23 ` Hans de Graaff
2011-09-20 8:00 ` Corentin Chary
2011-09-20 19:04 ` Donnie Berkholz
2011-09-21 8:57 ` Corentin Chary
2011-09-21 10:58 ` Markos Chandras
2011-09-21 12:05 ` Corentin Chary
2011-09-25 18:54 ` Corentin Chary
2011-09-26 18:42 ` Hans de Graaff
2011-09-28 5:41 ` Corentin Chary
2011-11-17 13:49 ` Corentin Chary
2011-04-19 7:29 ` Dirkjan Ochtman
2011-04-19 9:33 ` Corentin Chary
2011-09-06 18:20 ` Matt Turner
2011-09-07 7:32 ` Corentin Chary
2011-09-07 7:44 ` Michał Górny
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=BANLkTimfLTcAZBoEyYcXwBkJpZiH_3eiMA@mail.gmail.com \
--to=corentin.chary@gmail.com \
--cc=gentoo-dev@lists.gentoo.org \
--cc=graaff@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