[PATCH V2] push: propagate --new-branch and --ssh options when pushing subrepos
angel.ezquerra at gmail.com
Sat Oct 15 15:28:52 CDT 2011
On Sat, Oct 15, 2011 at 4:06 PM, Matt Mackall <mpm at selenic.com> wrote:
> Adding a bunch of new parameters here probably isn't the way to go. This
> probably needs to take an opts dict instead. And we should probably
> filter it in subrepo.py.
Do you mean that we should pass the opts dictionary that is one of the
arguments of the push function as is, and then simply use the relevant
arguments on the corresponding subrepo push method?
> Also, we shouldn't really do this without adding the same support on the
> pull/clone side.
That makes sense. I'll see what I can do.
In any case, which options do you think should be propagated down to
subrepos, in addition to --force and --new-branch? Also, should
subrepos that do not support a given option simply ignore it?
More information about the Mercurial-devel