public inbox for gentoo-soc@lists.gentoo.org
 help / color / mirror / Atom feed
From: Arun Raghavan <arunissatan@gmail.com>
To: gentoo-soc@lists.gentoo.org
Cc: ikelos@gentoo.org, bugday@gentoo.org, zmedico@gentoo.org,
	ruby@gentoo.org,  beandog@gentoo.org, damage@devloop.de,
	mikevalstar@gmail.com,  ycarus@zugaina.org, flameeyes@gentoo.org
Subject: Re: [gentoo-soc] Your part on ideas/issues for Google Summer of Code  2010
Date: Thu, 4 Mar 2010 12:47:04 +0530	[thread overview]
Message-ID: <6f8b45101003032317q14801060qb73d5135107c2191@mail.gmail.com> (raw)
In-Reply-To: <4B8EF8DA.6080609@gentoo.org>

On 4 March 2010 05:33, Sebastian Pipping <sping@gentoo.org> wrote:
[...]
> @all
> "upstream release tracker"  (brought up by ikelos on g-core recently)
> potential resources:
> - oswatershed
>  - http://oswatershed.org/
>  - http://github.com/tannewt/open-source-watershed
> - Debian watch files
>  - http://wiki.debian.org/DEHS
>  - http://manpages.debian.net/cgi-bin/man.cgi?query=uscan&sektion=1

There's bumpchecker too:
http://git.overlays.gentoo.org/gitweb/?p=proj/gentoo-bumpchecker.git;a=summary

Cheers,
-- 
Arun Raghavan
http://arunraghavan.net/
(Ford_Prefect | Gentoo) & (arunsr | GNOME)



  parent reply	other threads:[~2010-03-04  7:17 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-04  0:03 [gentoo-soc] Your part on ideas/issues for Google Summer of Code 2010 Sebastian Pipping
2010-03-04  7:13 ` [gentoo-soc] " Hans de Graaff
2010-03-26 22:18   ` Sebastian Pipping
2010-03-04  7:17 ` Arun Raghavan [this message]
2010-03-04  7:52   ` [gentoo-soc] " Nirbheek Chauhan
2010-03-05  0:21     ` Sebastian Pipping
2010-03-05  0:22   ` Sebastian Pipping
2010-03-05  6:21     ` Nirbheek Chauhan
2010-03-05  6:26       ` Nirbheek Chauhan
2010-03-28 18:15   ` Hans de Graaff
2010-03-05  5:20 ` [gentoo-soc] " Zac Medico
2010-03-05 15:43   ` Sebastian Pipping
2010-03-06  0:51     ` Zac Medico

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=6f8b45101003032317q14801060qb73d5135107c2191@mail.gmail.com \
    --to=arunissatan@gmail.com \
    --cc=beandog@gentoo.org \
    --cc=bugday@gentoo.org \
    --cc=damage@devloop.de \
    --cc=flameeyes@gentoo.org \
    --cc=gentoo-soc@lists.gentoo.org \
    --cc=ikelos@gentoo.org \
    --cc=mikevalstar@gmail.com \
    --cc=ruby@gentoo.org \
    --cc=ycarus@zugaina.org \
    --cc=zmedico@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