David Cantrell wrote:
On Mon, Apr 02, 2007 at 10:19:21AM -0500, Andy Lester wrote:
I recommend using Google Code hosting at code.google.com instead.
Setup is trivial, as is adding people to the project.
What's the advantage over sourceforge?
An important one is that it's possible to
On Apr 3, 2007, at 4:12 AM, David Cantrell wrote:
I recommend using Google Code hosting at code.google.com instead.
Setup is trivial, as is adding people to the project.
What's the advantage over sourceforge?
No waiting for project approval, and I've never had Google Code go
down. Also,
On Mon, Apr 02, 2007 at 10:19:21AM -0500, Andy Lester wrote:
I recommend using Google Code hosting at code.google.com instead.
Setup is trivial, as is adding people to the project.
What's the advantage over sourceforge?
--
David Cantrell | Cake Smuggler Extraordinaire
I remember when
Who do I need to contact to get access permission on svn.perl.org so I
can add the 'threads' and 'threads::shared' modules to it?
Sucker-punch spam with award-winning protection.
Try the free Yahoo! Mail
As with most things relating to Perl infrastructure, I'd start by
asking Ask: [EMAIL PROTECTED]
Regards,
David
On 4/2/07, Jerry D. Hedden [EMAIL PROTECTED] wrote:
Who do I need to contact to get access permission on svn.perl.org so I
can add the 'threads' and 'threads::shared' modules to it?
On Mon, Apr 02, 2007 at 10:29:12AM -0400, David Golden wrote:
As with most things relating to Perl infrastructure, I'd start by
asking Ask: [EMAIL PROTECTED]
Or, more generally, [EMAIL PROTECTED]
Tim.
Regards,
David
On 4/2/07, Jerry D. Hedden [EMAIL PROTECTED] wrote:
Who do I need to
On Apr 2, 2007, at 7:53 AM, Jerry D. Hedden wrote:
Who do I need to contact to get access permission on svn.perl.org so I
can add the 'threads' and 'threads::shared' modules to it?
I recommend using Google Code hosting at code.google.com instead.
Setup is trivial, as is adding people to
For my own modules, I might consider it, but for core
modules, I feel they should go somewhere more 'official'.
I thought that, too, but now I don't see that it makes a shred of
difference. If you see anything where it would make a difference,
even in perception, please let me know.
On Apr 2, 2007, at 11:16 AM, Jerry D. Hedden wrote:
If I should drop dead, someone in the Perl community could
take over the modules.
They can anyway. The repository at code.google.com is no less open
than svn.perl.org.
The big thing is that code.google.com takes the burden off of the
On Apr 2, 2007, at 2:19 PM, Tels wrote:
svn.perl.org sounds much
more officially perl than some random google URL,
So what?
plus you got two
repositories, which is never a good thing.
Why? We've got dozens of repositories right now. What's it matter
if it lives in svn.perl.org or
Jerry D. Hedden wrote:
Who do I need to contact to get access permission on
svn.perl.org so I can add the 'threads' and
'threads::shared' modules to it?
Andy Lester wrote:
I recommend using Google Code hosting at code.google.com
instead. Setup is trivial, as is adding people to the
Jerry D. Hedden wrote:
Jerry D. Hedden wrote:
Who do I need to contact to get access permission on
svn.perl.org so I can add the 'threads' and
'threads::shared' modules to it?
Andy Lester wrote:
I recommend using Google Code hosting at code.google.com
instead. Setup is trivial, as is
Jerry D. Hedden wrote:
Jerry D. Hedden wrote:
Who do I need to contact to get access permission on
svn.perl.org so I can add the 'threads' and
'threads::shared' modules to it?
Andy Lester wrote:
I recommend using Google Code hosting at code.google.com
instead. Setup is trivial, as is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Moin,
On Monday 02 April 2007 16:17:13 Andy Lester wrote:
On Apr 2, 2007, at 11:16 AM, Jerry D. Hedden wrote:
If I should drop dead, someone in the Perl community could
take over the modules.
They can anyway. The repository at code.google.com
14 matches
Mail list logo
