[PATCH] subrepo: don't push mercurial subrepositories unless necessary (issue3867)

[Angel Ezquerra]

On Mar 26, 2013 4:12 AM, "Sean Farley" <sean.michael.farley at gmail.com>
wrote:
>
>
> Bryan O'Sullivan writes:
>
> > On Mon, Mar 25, 2013 at 3:45 PM, Nathan Hoad <nathan at getoffmalawn.com
>wrote:
> >
> >> subrepo: don't push mercurial subrepositories unless necessary
(issue3867)
> >>
> >
> > This patch makes Mercurial perform a whole lot of extra work if some
> > changes must be pushed (it has to discover the set of changes to push
> > twice), but it does not reduce the amount of work done if nothing needs
to
> > be pushed. I believe you are trying to fix a non-bug.
>
> Well, I don't know about "non-bug" but Angel has a patch series (that
> needs some love) that tackles it another way:
>
> http://markmail.org/message/zt76am36n2yjiio6
>

Yes, the approach I took was proposed by Matt during the London sprint.

My series has already been reviewed by Augie, but I think he wanted someone
else to give his opinion as well. I'm waiting for comments on the latest
version that I sent a while ago.

BTW, this is a real issue. Push times when you have a fair number of
subrepos increase dramatically (proportionally to the number of subrepos).

Cheers,

Angel
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://selenic.com/pipermail/mercurial-devel/attachments/20130326/5cfbb13f/attachment.html>