Read Only Subrepos?

[Ryan Wilcox]

On Mon, Aug 9, 2010 at 1:54 PM, Steve Losh <steve at stevelosh.com> wrote:
> On Aug 9, 2010, at 1:35 PM, Matt Mackall wrote:
>
>> On Sat, 2010-08-07 at 09:57 -0400, Ryan Wilcox wrote:
>>> Hello everyone,
>>>
>>> I have set up a number of subrepos in my repository. These subrepos
>>> point to (open source) repositories where I have read only access.
[snip]
>>>
>>> Is there  way to configure Mercurial to not try to push those subrepos
>>> by default?
>>
>> Nope.
>>
>> When you commit at the top-level, you're taking a snapshot of a coherent
>> project state. That includes the state of your subrepos....

> Unless I'm reading Ryan's email wrong I think the issue is that the subrepos haven't been changed, so no changes
> actually need to be pushed, but Mercurial is trying anyway, failing, and then refusing to push the main repo.

Steve is correct: these are repositories where no changes have been
made (and in fact, I'll never make changes in them).

I absolutely understand that normally you'd want subrepos to be pushed
(coherent project state). In this case, I know I'll never make changes
to those subrepos, so I'm looking for a way to tell hg "this is a read
only subrepo, don't try pushing".

Does that help clarify my question?
_Ryan Wilcox

-- 
_____________________________________________________________________
Ryan Wilcox             PGP: 0x2F4E9C31
http://flavors.me/rwilcox