[PATCH 1 of 4 V2] schemas: add schemas to repositories
durham at fb.com
Fri Aug 9 16:09:50 CDT 2013
On 8/9/13 8:05 AM, "Augie Fackler" <raf at durin42.com> wrote:
>On Thu, Aug 08, 2013 at 08:51:33PM -0500, Matt Mackall wrote:
>> On Thu, 2013-08-08 at 16:31 -0700, Durham Goode wrote:
>> > # HG changeset patch
>> > # User Durham Goode <durham at fb.com>
>> > # Date 1375827328 25200
>> > # Tue Aug 06 15:15:28 2013 -0700
>> > # Node ID c683c90d00b124f985f4d8b3b51c65210317eb38
>> > # Parent 3e34e7b223d10bbe8814f82d7a1f53575fe09096
>> > schemas: add schemas to repositories
>> I think persisting schemas to disk is a bit premature. Also, in general,
>> I think schemas will be a property of the server, not the client.
>> Sometimes the client will use the schema when it's not doing an 'online'
>> operation, but all the existing schemas (ssh, http(s), etc.) don't.
>> Let's start with a patch that adds the schema namespace and a (possibly
>> trivial) way to register a schema with it.
Persisting the schema to disk is the most important part of this for me.
I need access to the schema information when users do any number of
operations (update, rebase, etc). Are you saying don't persist them to
disk by default, but in my extension I can wrap clone/pull then fetch the
schemas, and register to disk the ones that I am interested in?
>I'd still like to see this done as an out-of-tree extension until we
>can get a better sense of how it's going to work, rather than
>immediately commiting the mainline hg project to keeping it around.
I can make that happen.
>> Mathematics is the supreme nostalgia of our time.
>> Mercurial-devel mailing list
>> Mercurial-devel at selenic.com
More information about the Mercurial-devel