Non recursive update with subrepo's

[Raphael Sebbe]

That's actually the default behavior: "hg update" on parent also updates subrepos to their recorded versions. This is well documented, and works as expected. Having an example of that wouldn't bring interesting information IMO.

This is the right way of restoring a parent repository with all its subrepo to a given state. No problem on that. That's the "Restore" scenario.

My argument here is that there is another scenario, let call it "Daily Development", in which developers work on each repo and want to handle themselves the versions of each repo/subrepo (full control). However, in that use-case, whenever the parent repository is pulled/updated, it also updates the subrepo, which is cumbersome because developers have to go through each of the subrepo to update them back to the tip. That "Daily Development" scenario of not updating subrepo when updating parent repo is not possible at all in Mercurial (couldn't find options for it), yet it's the most common one for us. 

Don't misunderstand me, the "Restore" scenario is useful and should be preserved of course. But I think an option that would allow updating parent repository without updating subrepo would be an interesting option to have for daily development work.

Is my description more clear that way?

Best,

Raphael


On 27 Jan 2014, at 21:10, Matt Mackall <mpm at selenic.com> wrote:

> On Sat, 2014-01-25 at 15:22 +0100, Raphael Sebbe wrote:
>> Hi all,
>> 
>> Does anyone know if it is possible to update a parent repository *without* updating/pulling its subrepos?
>> 
>> Our use case is that we have a main project with dependencies
>> (subrepo), all evolving simultaneously with multiple developers, and
>> always want repositories to be at their most advanced local revision,
>> which can be in ahead of a subrepo version that was pushed previously
>> (don't want to go back when updating the parent).
>> 
>> I fully understand the value of updating the subrepos when building a
>> previous version of the app, want to update all to their sync state.
>> However, in our use case during development phase, this is cumbersome,
>> as each time we pull/update the parent, subrepos are going back and we
>> have to update each of them manually to their latest local revision.
> 
> Hmm. Going "back" sounds like a bug. Can you construct a minimal
> demonstration of your issue for a bug report?
> 
> -- 
> Mathematics is the supreme nostalgia of our time.