git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH] Make 'remote show' distinguish between merged and rebased remote branches

From
Junio C Hamano <gitster@pobox.com>
Date
Feb 10, 2009, 21:17 UTC
Message-ID
<7v3aemm1po.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<20090210202046.8EBEC3360AC@rincewind>
Marc Branchaud <marcnarc@xiplink.com> writes:
Show 17 quoted lines
> Prints "rebased" instead of "merged" if branch.<name>.rebase is true.
>
> Signed-off-by: Marc Branchaud <marcnarc@xiplink.com>
> ...
> 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".

Previous: Marc BranchaudNext: Marc Branchaud
Message 2 of 9 in “Make 'remote show' distinguish between merged and rebased remote branches”
  1. Make 'remote show' distinguish between merged and rebased remote branchesMarc Branchaud, Feb 10, 2009
  2. Junio C HamanoFeb 10, 2009
  3. Marc BranchaudFeb 10, 2009
  4. Jay SoffianFeb 10, 2009
  5. Marc BranchaudFeb 11, 2009
  6. Johannes SixtFeb 11, 2009
  7. Junio C HamanoFeb 11, 2009
  8. Marc BranchaudFeb 11, 2009
  9. Johannes SchindelinFeb 10, 2009

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.