From: Marc Branchaud <marcnarc@xiplink.com>
To: Jay Soffian <jaysoffian@gmail.com>
Cc: git@vger.kernel.org, Junio C Hamano <gitster@pobox.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>,
Johannes Sixt <j.sixt@viscovery.net>
Subject: Re: [PATCH 4/4] remote: new show output style
Date: Thu, 19 Feb 2009 11:03:08 -0500 [thread overview]
Message-ID: <499D82BC.7020500@xiplink.com> (raw)
In-Reply-To: <1235020471-59982-5-git-send-email-jaysoffian@gmail.com>
Jay, thanks a ton! I'd been poking at this myself off and on over the last week -- I'm very glad to see you've done the work!
A couple of suggestions on the new format:
Jay Soffian wrote:
>
> @@ -137,21 +137,18 @@ cat > test/expect << EOF
> * remote origin
> URL: $(pwd)/one
> HEAD branch: master
> - Remote branch merged with 'git pull' while on branch master
> - master
> - New remote branch (next fetch will store in remotes/origin)
> - master
> - Tracked remote branches
> - master
> - side
> - Local branches pushed with 'git push'
> + Remote branches:
> + master new (next fetch will store in remotes/origin)
> + side tracked
> + Local branches configured for 'git pull':
> + foo rebases onto remote master
> + master merges w/remote master
> + Local branches configured for 'git push':
> master:upstream
> +refs/tags/lastbackup
> * remote two
> URL: ../two
> - HEAD branches:
> - another
> - master
> + HEAD branches: another, master
> EOF
First, a nit: I don't know if the "w/remote" notation makes sense to non-English speakers. I also like the alignment achieved by "merges with remote " (note the trailing space).
Second, I think it would be good to also change the format of the 'git push' list, for consistency:
Local branches configured for 'git push':
master fast-forwards remote upstream
refs/tags/lastbackup updates remote refs/tags/lastbackup
Though I'm not really happy using "updates" when + is specified in the push refspec. What, precisely, is a "non-fast forward update" anyway? Is it essentially a rebase? If so, maybe "rebases onto remote " would be better (again with a trailing space to get nice alignment).
Thanks again!
M.
next prev parent reply other threads:[~2009-02-19 16:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-02-19 5:14 [PATCH 0/4] Improve "remote show" output Jay Soffian
2009-02-19 5:14 ` [PATCH 1/4] remote: minor code cleanups in preparation for changing "show" output Jay Soffian
2009-02-19 5:14 ` [PATCH 2/4] remote: move append_ref_to_tracked_list to get rid of prototype Jay Soffian
2009-02-19 5:14 ` [PATCH 3/4] string-list: add for_each_string_list() Jay Soffian
2009-02-19 5:14 ` [PATCH 4/4] remote: new show output style Jay Soffian
2009-02-19 16:03 ` Marc Branchaud [this message]
2009-02-19 16:16 ` Sverre Rabbelier
2009-02-19 16:31 ` Marc Branchaud
2009-02-19 16:33 ` Sverre Rabbelier
2009-02-19 16:17 ` Rostislav Svoboda
2009-02-19 17:57 ` Jay Soffian
2009-02-19 17:59 ` Jay Soffian
2009-02-19 18:58 ` Julian Phillips
2009-02-20 22:34 ` Marc Branchaud
2009-02-20 22:55 ` Jay Soffian
2009-02-19 19:29 ` Johannes Sixt
2009-02-19 19:51 ` Jay Soffian
2009-02-20 7:19 ` [PATCH 1/4] remote: minor code cleanups in preparation for changing "show" output Junio C Hamano
2009-02-20 10:50 ` Jay Soffian
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=499D82BC.7020500@xiplink.com \
--to=marcnarc@xiplink.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=j.sixt@viscovery.net \
--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.