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
Johannes Sixt <j.sixt@viscovery.net>
Date
Feb 11, 2009, 17:12 UTC
Message-ID
<499306F7.8050404@viscovery.net>
In-Reply-To
<499303E8.6030000@xiplink.com>
Marc Branchaud schrieb:
Show 15 quoted lines
> Jay Soffian wrote:
>> * remote origin
>>   URL: git://git.kernel.org/pub/scm/git/git.git
>>   Remote branches:
>>     html      Not tracked
>>     maint     Tracked
>>     man       Tracked
>>     master    Tracked
>>     next      Tracked
>>     pu        Tracked
>>     todo      Not tracked
>>     old-next  Stale (would prune)
>>   Local branches configured to pull from this remote:
>>     master           upstream is master (merges)
>>     wip/remote-HEAD  upstream is next   (rebases)

I find this form more useful than the one below because of the clear separation into remote an local branchs.

Show 15 quoted lines
> How about something a bit tighter, merging the local branch list with the remote branch list:
> 
> * remote origin
>   URL: git://git.kernel.org/pub/scm/git/git.git
>   Remote branches:
>     html      Not tracked
>     master    Tracked by local branches:
>                 master (merges)
>                 mywork (rebases)
>     next      Tracked by local branch:
>                 wip/remote-HEAD (rebases)
>     pu        Tracked by local branch:
>                 pu (merges)
>     todo      Not tracked
>     old-next  Stale (would prune)
-- Hannes
Previous: Marc BranchaudNext: Junio C Hamano
Message 6 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.