[PATCH] schemes extension

Augie Fackler durin42 at gmail.com
Tue Nov 24 10:04:37 CST 2009


On Tue, Nov 24, 2009 at 9:55 AM, Alexander Solovyov
<piranha at piranha.org.ua> wrote:
> On Tue, Nov 24, 2009 at 5:49 PM, Alexander Solovyov
> <piranha at piranha.org.ua> wrote:
>> # HG changeset patch
>> schemes extension
>
> I would love to see it included, as I use it myself everyday and heard that
> others do the same. :-)
>
> Test is pretty simple, it just tests that basic functionality does work. I'm not
> sure if this is stopper, it is just hard to emulate all possibilities.
>
>> +Additionally there is support for some more complex schemas, for example used
>> +by Google Code::
>> +
>> +  [schemes]
>> +  gcode = http://{project}.googlecode.com/hg/
>> +
>> +The syntax is taken from Mercurial templates, there are two variables present,
>> +namely {project} and {repo}, which are determined from the url you're supplying:
>> +gcode://project/repo.
>> +"""
>
> And I'm not sure about this part... Does {project} and {repo} sound like an
> appropriate choice here? It's user and repo in case of bitbucket, for
> example. Maybe I should use something like {parent} and {path} here?

I'd rather not use {parent} here - it really is project, since there
are also "user clones" on Google Code now, which have a notion of a
parent repository that is different.

>
> --
> Alexander
> _______________________________________________
> Mercurial-devel mailing list
> Mercurial-devel at selenic.com
> http://selenic.com/mailman/listinfo/mercurial-devel
>


More information about the Mercurial-devel mailing list