Re: [PATCH 1/8] Make the "traditionally-supported" URLs a special case

From: Johannes Schindelin <johannes.schindelin@gmx.de>
Date: Sep 4, 2009, 21:08 UTC
Message-ID: <alpine.DEB.1.00.0909042305390.8306@pacific.mpi-cbg.de>
In-Reply-To: <fabb9a1e0909041235x74a3b9b4gf65e650ca0d00831@mail.gmail.com>

Hi,

On Fri, 4 Sep 2009, Sverre Rabbelier wrote:

Show 12 quoted lines

> On Fri, Sep 4, 2009 at 21:05, Daniel Barkalow<barkalow@iabervon.org> 
> wrote:
> > Some foreign vcses, including the only one I ever personally use, do 
> > not have URLs, and require a bunch of options and paths to specify a 
> > repository. I don't want to have to use:
> >
> >        url = p4://rsh:ssh+-q+-a+-x+-l+p4ssh+-q+-x+perforce+%2Fbin%2Ftrue//projects/foo/bar-1.0/...,//projects/foo/bar-1.1/...
> 
> Btw, doesn't p4 have these config files that you can download that 
> contain the configuration? In that case 
> 'p4://example.org/p4/main-development.configfile' would be very 
> convenient.

If that's how p4 users initialize their working directories, then that is the way to go.

And I cannot start to believe that the complicated way you described is the common way to initialize p4 working directories, as that would tempt the intelligence/enthusiasm of the average programmer.

Show 8 quoted lines

> > For cases where the foreign vcs has something to put in the "url" 
> > spot, you don't need to set "vcs". In fact, you are only allowed to 
> > set one or the other of "vcs" and "url" with my current version. What 
> > you're interested in is explicitly left for later, when we have a 
> > prototype helper for such a foreign vcs and can try it out with 
> > potential users.
> 
> I need to hurry up and get working on that hg implementation then :).

Indeed you do. If only to prove that _this_ and the likes are something to optimize for, not some obscure vcs config variable that only introduces a little-exercized code path that's _prone_ to break and does not help anybody.

Ciao, Dscho