[PATCH] subrepo: pull subrepos recursively, and support pull from clones (issue2024)

Martin Geisler mg at lazybytes.net
Tue Jul 13 03:45:54 CDT 2010


Pradeepkumar Gayam <in3xes at gmail.com> writes:

> On Mon, Jul 12, 2010 at 11:56 PM, Martin Geisler <mg at lazybytes.net> wrote:
>
>> Pradeepkumar Gayam <in3xes at gmail.com> writes:
>>
>> > # HG changeset patch
>> > # User Pradeepkumar Gayam <in3xes at gmail.com>
>> > # Date 1278801299 -19800
>> > # Node ID ed3ea5d08f64b0b4ea94353ca42cfa6f07e8f38f
>> > # Parent  f4eddec324b755a45ea71570c7c8dc63bcbdfc1a
>> > subrepo: pull subrepos recursively, and support pull from clones
>> (issue2024)
>> >
>> > diff -r f4eddec324b7 -r ed3ea5d08f64 mercurial/commands.py
>> > --- a/mercurial/commands.py   Fri Jul 09 14:21:45 2010 +0200
>> > +++ b/mercurial/commands.py   Sun Jul 11 04:04:59 2010 +0530
>> > @@ -2798,6 +2798,19 @@
>> >              raise util.Abort(err)
>> >
>> >      modheads = repo.pull(other, heads=revs, force=opts.get('force'))
>> > +
>> > +    if opts.get('subrepo'):
>> > +        c = repo[repo.changelog.node(len(repo)-1)]
>>
>> I guess this means that you suggest we pull all the subrepositories
>> present in tip? Would it not be more logical to pull those present in
>> the current working directory?
>>
>> Yes, that makes sense.
>
> I think you are working on subrepos. So, shall I resend the patch or
> you already have something similar to this?

Yes, I'm looking at extending subrepository support for pull and other
commands. But I have not looked at pull yet.

-- 
Martin Geisler

aragost Trifork
Professional Mercurial support
http://aragost.com/mercurial/


More information about the Mercurial-devel mailing list