This is the first fix, but it's obvious this is what we want: if a user creates
a new branch with git:
% git checkout -b branches/devel
And then pushes this branch
% git push origin branches/devel
(which is the way to push new mercurial branches)
We obviously want to create a branch, but the command would fail, and the fix
is simple: tell the push that we might create new branches.
This only matters when foce_push=False.
Can't possibly introduce regressions, unless you think of the ability to push
new branches as a regression.
Felipe Contreras wrote:
> When force_push is disabled, we need to turn the argument to True.
> Signed-off-by: Felipe Contreras <felipe.contre...@gmail.com>
> contrib/remote-helpers/git-remote-hg | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
> diff --git a/contrib/remote-helpers/git-remote-hg
> index 4a5c72f..3cf9b4c 100755
> --- a/contrib/remote-helpers/git-remote-hg
> +++ b/contrib/remote-helpers/git-remote-hg
> @@ -856,7 +856,7 @@ def do_export(parser):
> if peer:
> - parser.repo.push(peer, force=force_push)
> + parser.repo.push(peer, force=force_push, newbranch=True)
> # handle bookmarks
> for bmark, node in p_bmarks:
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html