[PATCH 0 of 5 ] subrepo: add --subrev option to clone and pull commands

Angel Ezquerra angel.ezquerra at gmail.com
Thu Jan 16 00:36:29 CST 2014

On Wed, Jan 15, 2014 at 2:24 PM, Matt Mackall <mpm at selenic.com> wrote:
> On Tue, 2014-01-14 at 21:01 -0800, Angel Ezquerra wrote:
>> On Tue, Jan 14, 2014 at 11:02 AM, Matt Mackall <mpm at selenic.com> wrote:
>> > On Sat, 2013-11-23 at 21:27 +0100, Angel Ezquerra wrote:
>> >> This is a rework of a patch series that I sent a while ago. This tries to take into account the feedback that mpm gave me at the time.
>> >
>> > I assume this all implicitly depends on the caching patches?
>> No, the 3 different subrepo related patch series that I sent a while
>> ago are completely independent.
> Ok.. then where does it put subrepos that are not present in the working
> directory and/or conflict?

Subrepos that are not present on the working directory are placed on
the working directory, as they would if you updated to the
corresponding parent repository revision. If there is a conflict (or
any other sort of problem during the subrepo pull/clone) the
corresponding exception will be caught, a warning message will be
shown and the process will continue.

I think this is fine since it similar to what would happen if you did
not use the --subrev option and updated to the corresponding revision
after the fact.

If this series were used in combination with the subrepo cache series
then it could be possible to just place them on the cache and not on
the working directory.


More information about the Mercurial-devel mailing list