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
Jay Soffian <jaysoffian@gmail.com>
Date
Feb 10, 2009, 23:13 UTC
Message-ID
<76718490902101513i504e515ocb4a2d789ba520f0@mail.gmail.com>
In-Reply-To
<4991FA18.1040200@xiplink.com>
On Tue, Feb 10, 2009 at 5:05 PM, Marc Branchaud <marcnarc@xiplink.com> wrote:
Show 12 quoted lines
> I'm happy to use more accurate phrasing -- I was just going for a minimal change.
>
> How about the following, consistent for both cases:
>
> 'git pull' merges branch master with remote branch
>  master
> 'git pull' rebases branch rebaser on top of remote branch
>  side
>
> ?
>
> I like the above because the keywords & branch names are in consistent locations, making it easier to parse the output.

The output of git remote show seems much too verbose for the information it provides. Something like this, I think, provides the same information in much less space:

* 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)

When run with "-n" the status column would be blank or say "Status not available with -n".

$0.02. :-)
j.
Previous: Marc BranchaudNext: Marc Branchaud
Message 4 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.