Marc Branchaud <marcnarc@xxxxxxxxxxx> writes: > Prints "rebased" instead of "merged" if branch.<name>.rebase is true. > > Signed-off-by: Marc Branchaud <marcnarc@xxxxxxxxxxx> > ... > diff --git a/t/t5505-remote.sh b/t/t5505-remote.sh > index 1f59960..be0316a 100755 > --- a/t/t5505-remote.sh > +++ b/t/t5505-remote.sh > @@ -112,6 +112,8 @@ cat > test/expect << EOF > URL: $(pwd)/one > Remote branch merged with 'git pull' while on branch master > master > + Remote branch rebased with 'git pull' while on branch rebaser > + side > New remote branch (next fetch will store in remotes/origin) > master > Tracked remote branches I sympathize with what you are trying to do but I do not think this is correct. You will *never* rebase remote on top of your changes; rather you will replay your changes on top of what the updated remote has. It is more like "if you start git pull while on branch rebaser, it will rebased on top of this branch from the remote". -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
