git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Johannes Sixt <j.sixt@viscovery.net>
Cc: Marc Branchaud <marcnarc@xiplink.com>,
	Jay Soffian <jaysoffian@gmail.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 09:35:13 -0800	[thread overview]
Message-ID: <7vab8sg9m6.fsf@gitster.siamese.dyndns.org> (raw)
In-Reply-To: <499306F7.8050404@viscovery.net> (Johannes Sixt's message of "Wed, 11 Feb 2009 18:12:23 +0100")

Johannes Sixt <j.sixt@viscovery.net> writes:

> Marc Branchaud schrieb:
>> 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.

Good point.

  reply	other threads:[~2009-02-11 17:36 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
2009-02-11 17:12         ` Johannes Sixt
2009-02-11 17:35           ` Junio C Hamano [this message]
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=7vab8sg9m6.fsf@gitster.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=j.sixt@viscovery.net \
    --cc=jaysoffian@gmail.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).