public inbox for linux-i2c@vger.kernel.org
 help / color / mirror / Atom feed
From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
	Paul Goyette <paul-3orOWTcw9wBWk0Htik3J/w@public.gmane.org>
Subject: Re: New home for i2c-tools (RFC)
Date: Thu, 29 Jan 2009 17:28:12 +0100	[thread overview]
Message-ID: <20090129172812.22c3d301@hyperion.delvare> (raw)
In-Reply-To: <200901291056.12963.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>

Hi Mike,

On Thu, 29 Jan 2009 10:56:10 -0500, Mike Frysinger wrote:
> On Thursday 29 January 2009 04:37:17 Jean Delvare wrote:
> > And there are other options available, such as Gna! or BerliOS. Never
> > used these myself though.
> >
> > [2] https://gna.org/
> > [3] http://developer.berlios.de/
> >
> > As far as I am concerned, I can live with all options, but what I
> > really want to know is: which option would potential future
> > contributors prefer? Please speak up if you care!
> 
> any reason for not looking at sf.net ?  they provide svn and everything else 
> needed ... they dont provide git currently though so an easy upgrade path like 
> is available with berlios is out of the question.

Sourceforge is fat and slow and their mailing lists are filled up with
spam. I have had too much trouble with that site as a user in the past
so I did not even consider it as an option as a developer.

> a quick survey based on packages in gentoo shows sf.net is significantly more 
> popular atm than berlios and gna (combined even).

I'm not surprised, Sourceforge is really big. Probably berlios is
essentially popular in Germany and gna essentially popular in France.

> but yes, i could live with any of those sites ...

Thanks,
-- 
Jean Delvare

  parent reply	other threads:[~2009-01-29 16:28 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-29  9:37 New home for i2c-tools (RFC) Jean Delvare
     [not found] ` <20090129103717.025661db-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-01-29 11:15   ` Wolfram Sang
2009-01-29 15:56   ` Mike Frysinger
     [not found]     ` <200901291056.12963.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2009-01-29 16:00       ` Paul Goyette
2009-01-29 16:28       ` Jean Delvare [this message]
     [not found]         ` <20090129172812.22c3d301-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-01-29 16:30           ` Wolfram Sang
     [not found]             ` <20090129163039.GF32057-bIcnvbaLZ9MEGnE8C9+IrQ@public.gmane.org>
2009-01-29 16:38               ` Tony Lindgren
     [not found]                 ` <20090129163845.GC32148-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2009-01-29 16:48                   ` Mike Frysinger
     [not found]                     ` <200901291148.06805.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2009-01-29 16:56                       ` Tony Lindgren
     [not found]                         ` <20090129165615.GJ32148-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>
2009-01-29 17:10                           ` Mike Frysinger

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=20090129172812.22c3d301@hyperion.delvare \
    --to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=paul-3orOWTcw9wBWk0Htik3J/w@public.gmane.org \
    --cc=vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.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