git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 4/4] remote: new show output style

From
Jay Soffian <jaysoffian@gmail.com>
Date
Feb 19, 2009, 17:57 UTC
Message-ID
<76718490902190957td40d425p6b2ae1242060114d@mail.gmail.com>
In-Reply-To
<499D82BC.7020500@xiplink.com>
On Thu, Feb 19, 2009 at 11:03 AM, Marc Branchaud <marcnarc@xiplink.com> wrote:
> 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).
I tried out a few different option and none was very satisfactory to me.
1)
    master            rebases onto remote master
    another-branch    merges with remote  next
    some-other-branch rebases onto remote master
Here, the unaligned "with" and "onto" is ugly.
2)
    master            rebases onto remote master
    another-branch    merges  with remote next
    some-other-branch rebases onto remote master

This looks better to me. However, if none of your branches rebase, then the extra space looks like it is a mistake. e.g.:

    master            merges  with remote master
    another-branch    merges  with remote next
    some-other-branch merges  with remote master

I could add code to detect whether all the branches merge and then not output the space, but, sigh. And I couldn't think of any other combination of words that had the same character spacing.

So that's how I ended up with "merges w/remote". This is also slightly less wide. I always try to have output fit into 80 columns (how quaint, I know) and a merging branch might have multiple upstreams. e.g.

   another-branch merges w/foo, bar, baz

IOW, the output in the patch wasn't arbitrary. I did think about it quite a bit. Which isn't to say it's right, just it's the best I came up with.

I'm somewhat confused by "w/remote" making sense to non-English speakers as it's English output.

> Second, I think it would be good to also change the format of the 'git push'
> list, for consistency:

I left that out on purpose. The only folks with push refspecs put them their manually, and the raw refspec is clearer and more concise than any English words can convey. That was my reasoning anyway.

Thanks for the feedback.
j.
Previous: Rostislav SvobodaNext: Jay Soffian
Message 11 of 19 in “Improve "remote show" output”
  1. 0/4 Improve "remote show" outputJay Soffian, Feb 19, 2009
  2. 1/4 remote: minor code cleanups in preparation for changing "show" outputJay Soffian, Feb 19, 2009
  3. 2/4 remote: move append_ref_to_tracked_list to get rid of prototypeJay Soffian, Feb 19, 2009
  4. 3/4 string-list: add for_each_string_list()Jay Soffian, Feb 19, 2009
  5. 4/4 remote: new show output styleJay Soffian, Feb 19, 2009
  6. Marc BranchaudFeb 19, 2009
  7. Sverre RabbelierFeb 19, 2009
  8. Marc BranchaudFeb 19, 2009
  9. Sverre RabbelierFeb 19, 2009
  10. Rostislav SvobodaFeb 19, 2009
  11. Jay SoffianFeb 19, 2009
  12. Jay SoffianFeb 19, 2009
  13. Julian PhillipsFeb 19, 2009
  14. Marc BranchaudFeb 20, 2009
  15. Jay SoffianFeb 20, 2009
  16. Johannes SixtFeb 19, 2009
  17. Jay SoffianFeb 19, 2009
  18. Junio C HamanoFeb 20, 2009
  19. Jay SoffianFeb 20, 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.