Path expansion in the .hgsub file

Martin Geisler mg at lazybytes.net
Thu Jul 15 14:26:58 UTC 2010


Dirkjan Ochtman <dirkjan at ochtman.nl> writes:

> On Thu, Jul 15, 2010 at 15:36, Martin Geisler <mg at lazybytes.net> wrote:
>> - put the [sub-paths] section into the .hgsub file.
>>
>>  The .hgsub file is read first followed by the other hgrc files. This
>>  gives us a way to provide default paths and we can update those
>>  defaults by changing .hgsub as we go along. Users can still override
>>  the defaults as needed.
>
> This sounds like the sane solution.

Yeah, I also like this one for it's simplicity. I'll give it a go...

>> - store the paths using the new pushkey infrastructure in Mercurial 1.6.
>>
>>  Jonny asked for a .hg/etc directory where we can put config data that
>>  should live outside of the normal history -- the pushkey concept gives
>>  us exactly that.
>
> Remember that pushkeys so far are just infrastructure for the wire
> protocol. I'm kind of getting the vibe that pushkeys are the new
> hammer to hit all nails with, but there's no generic storage mechanism
> for them (nor should there necessarily be one). Let's please think in
> terms of actual problems, and only then verify if pushkeys are the
> right mechanism to help out the transfer part. </grumpy-old-man-rant>

Hehe :-) You are right as far as I see pushkeys as the general mechanism
that we'll use in the future to transfer out-of-history information.

-- 
Martin Geisler

Mercurial links: http://mercurial.ch/
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 197 bytes
Desc: not available
URL: <http://lists.mercurial-scm.org/pipermail/mercurial/attachments/20100715/5668d70e/attachment.asc>


More information about the Mercurial mailing list