Non recursive update with subrepo's
Raphael Sebbe
raphael.sebbe at gmail.com
Thu Jan 30 14:47:59 UTC 2014
On 30 Jan 2014, at 14:18, Kastner Masilko, Friedrich <kastner-masilko at at.festo.com> wrote:
>> From: mercurial-bounces at selenic.com [mailto:mercurial-bounces at selenic.com] On Behalf Of Raphael Sebbe
>>
>> 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.
>
> I use this "daily development" scenario every day at work, and it is no problem at all. Mercurial will just recognise the changed subrepos as dirty working-copy (as it should), and "merge" the new update-version into the working-copy if the standard update-and-merge strategy is applicable.
>
> Do you perhaps use "-C" all the time?
>
> Regards,
> Fritz
Hi Fritz,
I will double-check that, it's possible. I use it mostly through a UI (SourceTree), so I need to verify that.
Raphael
More information about the Mercurial
mailing list