From: Marc Branchaud <marcnarc@xiplink.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>,
git@vger.kernel.org, Johannes.Schindelin@gmx.de
Subject: Re: [PATCH] Make 'remote show' distinguish between merged and rebased remote branches
Date: Wed, 11 Feb 2009 11:59:20 -0500 [thread overview]
Message-ID: <499303E8.6030000@xiplink.com> (raw)
In-Reply-To: <76718490902101513i504e515ocb4a2d789ba520f0@mail.gmail.com>
Jay Soffian wrote:
>
> The output of git remote show seems much too verbose for the
> information it provides.
I agree.
I'm happy to hammer out and implement new output for 'remote show', but is there any chance that such a change would be accepted?
Junio, Dscho, (others) -- any opposition to this?
> 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)
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)
?
M.
next prev parent reply other threads:[~2009-02-11 17:00 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-10 17:08 [PATCH] Make 'remote show' distinguish between merged and rebased remote branches Marc Branchaud
2009-02-10 21:17 ` Junio C Hamano
2009-02-10 22:05 ` Marc Branchaud
2009-02-10 23:13 ` Jay Soffian
2009-02-11 16:59 ` Marc Branchaud [this message]
2009-02-11 17:12 ` Johannes Sixt
2009-02-11 17:35 ` Junio C Hamano
2009-02-11 21:35 ` Marc Branchaud
2009-02-10 21:22 ` Johannes Schindelin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=499303E8.6030000@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jaysoffian@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.