Re: [Python-Dev] Source control tools

2006-06-18 Thread Andrew Bennetts
On Thu, Jun 15, 2006 at 10:33:49PM +0200, Alexander Schremmer wrote: > On Thu, 15 Jun 2006 19:00:09 +0200, Jan Claeys wrote: > > > Op di, 13-06-2006 te 10:27 +0200, schreef Alexander Schremmer: > >> Bazaar-NG seems to reach limits already when working on > >> it's own code/repository. > > > > Ca

Re: [Python-Dev] Source control tools

2006-06-18 Thread Nicolas Chauvat
On Tue, Jun 13, 2006 at 10:27:17AM +0200, Alexander Schremmer wrote: > Maybe you benchmarked a Tailor deficiency here, but Mercurial scales very > well. People use it for work on the Linux kernel etc. > Compared to that, Bazaar-NG seems to reach limits already when working on > it's own code/reposi

Re: [Python-Dev] Source control tools

2006-06-15 Thread Alexander Schremmer
On Thu, 15 Jun 2006 19:00:09 +0200, Jan Claeys wrote: > Op di, 13-06-2006 te 10:27 +0200, schreef Alexander Schremmer: >> Bazaar-NG seems to reach limits already when working on >> it's own code/repository. > > Canonical uses bzr to develop launchpad.net, which is a "little bit" > larger dan bzr

Re: [Python-Dev] Source control tools

2006-06-15 Thread Jan Claeys
Op di, 13-06-2006 te 10:27 +0200, schreef Alexander Schremmer: > Bazaar-NG seems to reach limits already when working on > it's own code/repository. Canonical uses bzr to develop launchpad.net, which is a "little bit" larger dan bzr itself, I suspect...? -- Jan Claeys

Re: [Python-Dev] Source control tools

2006-06-13 Thread Alexander Schremmer
On Mon, 12 Jun 2006 23:31:14 +0200, Thomas Wouters wrote: > I did partial imports into Mercurial and Bazaar-NG, but I got interrupted > and couldn't draw any conclusions -- although from looking at the > implementation, I don't think they'd scale very well at the moment (but that > could probably

Re: [Python-Dev] Source control tools

2006-06-12 Thread Giovanni Bajo
Thomas Wouters <[EMAIL PROTECTED]> wrote: >> It would be an important move towards world peace, if it didn't >> inspire whole new SCM-holy-wars :-) I have a fair bit of experience with >> different >> SCM (VC, source control tool, however you want to call them) so I'll >> take >> this opportunity

Re: [Python-Dev] Source control tools

2006-06-12 Thread Thomas Wouters
On 6/13/06, Oleg Broytmann <[EMAIL PROTECTED]> wrote: On Mon, Jun 12, 2006 at 11:31:14PM +0200, Thomas Wouters wrote:> First of all, changing SCM means changing how everyone works.   Distributed branches is not the only requirement. Oh, I know, no worries about that.  There are also:-- subtree auth

Re: [Python-Dev] Source control tools

2006-06-12 Thread Oleg Broytmann
On Mon, Jun 12, 2006 at 11:31:14PM +0200, Thomas Wouters wrote: > First of all, changing SCM means changing how everyone works. Distributed branches is not the only requirement. There are also: -- subtree authorization (different access rights in different parts of the tree); in distributed

Re: [Python-Dev] Source control tools

2006-06-12 Thread Guido van Rossum
On 6/12/06, Thomas Wouters <[EMAIL PROTECTED]> wrote: > [*] Short? This whole mail was short! I can talk for hours about the benefit > of proper branches and what kind of stuff is easier, better and more > efficient with them. I can draw huge ASCII diagrams explaining the > fundamental difference b

Re: [Python-Dev] Source control tools

2006-06-12 Thread Brett Cannon
On 6/12/06, Thomas Wouters <[EMAIL PROTECTED]> wrote: On 6/12/06, Guido van Rossum <[EMAIL PROTECTED] > wrote: Perhaps issues like these should motivate us to consider a differentsource control tool. There's a new crop of tools out that could solvethis by having multiple repositories that can be sy

Re: [Python-Dev] Source control tools

2006-06-12 Thread Thomas Wouters
On 6/12/06, Guido van Rossum <[EMAIL PROTECTED]> wrote: Perhaps issues like these should motivate us to consider a differentsource control tool. There's a new crop of tools out that could solvethis by having multiple repositories that can be sync'ed with eachother. This sounds like an important mov