From: Jay Soffian <jaysoffian@gmail.com>
To: Marc Branchaud <marcnarc@xiplink.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Make 'remote show' distinguish between merged and rebased remote branches
Date: Tue, 10 Feb 2009 18:13:52 -0500 [thread overview]
Message-ID: <76718490902101513i504e515ocb4a2d789ba520f0@mail.gmail.com> (raw)
In-Reply-To: <4991FA18.1040200@xiplink.com>
On Tue, Feb 10, 2009 at 5:05 PM, Marc Branchaud <marcnarc@xiplink.com> wrote:
> 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.
next prev parent reply other threads:[~2009-02-10 23:15 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 [this message]
2009-02-11 16:59 ` Marc Branchaud
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=76718490902101513i504e515ocb4a2d789ba520f0@mail.gmail.com \
--to=jaysoffian@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=marcnarc@xiplink.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).