Michael G Schwern writes: > Could we split this off into a working group and mailing list seperate > from perl6-meta? Sure. I'm going to set an aggressive schedule for the decision, though, because this has all the hallmarks of a religious war. Let's work through the problems now and be forced to end the debate after a reasonable time period. List: [EMAIL PROTECTED] Chair: Dan Sugalski <[EMAIL PROTECTED]> Deadline: 18 September 2000 Mission: To decide the source control system (Perforce, CVS, etc) to be used for perl6 development. Dan's chair not because I want to stack the odds in favour of one thing over another, but because he's been taking the lead in source issues so far. Ask, please work your mailing list magic. Thanks, Nat
- Re: code repository Dan Sugalski
- Re: code repository Bradley M. Kuhn
- Re: code repository Bennett Todd
- Re: code repository Dan Sugalski
- Re: code repository Bennett Todd
- Re: code repository Dan Sugalski
- Re: code repository Alan Burlison
- Re: code repository Adam Turoff
- Re: code repository Nathan Torkington
- Re: code repository Michael G Schwern
- Re: code repository Nathan Torkington
- Re: code repository Bennett Todd
- Re: code repository Dan Sugalski
- Re: code repository Adam Turoff
- Can perforce gateway to CVS without loss of... Bradley M. Kuhn
- Re: Can perforce gateway to CVS without los... Dan Sugalski
- Can perforce gateway to CVS without loss of... Nick Ing-Simmons
- Re: Can perforce gateway to CVS without los... Barrie Slaymaker
- Re: Can perforce gateway to CVS without los... Barrie Slaymaker
- Re: code repository Adam Turoff
- Re: code repository Bradley M. Kuhn