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

Re: [PATCH 5/5] fetch: Clean output

From
SSanti <sbejar@gmail.com>
Date
Sep 30, 2006, 09:42 UTC
Message-ID
<8aa486160609300242i6f52ee90o235e668a5d865fb7@mail.gmail.com>
In-Reply-To
<7vpsdehzcs.fsf@assigned-by-dhcp.cox.net>
2006/9/30, Junio C Hamano <junkio@cox.net>:
Show 13 quoted lines
> Santi Béjar <sbejar@gmail.com> writes:
>
> > Do not show duplicated remote branch information and reformat the output as:
> >
> > $ git fetch -v   # the committish lines for the -v.
> > * refs/heads/origin: fast forward to remote branch 'master' of ../git/
> >   1ad7a06..bc1a580
> >   committish: bc1a580
>
> I am not quite sure about this --- it is not obvious what these
> two numbers represent anymore.  Also I think the last line
> outlived its usefulness (99% of the time refs are committish, so
> noting exception is good but otherwise it is not interesting).

I agree in the case of updating a ref, but I would keep it otherwise (and even in this case only when -v is given).

Show 9 quoted lines
>
> I know you opted for minimum patch, but it might be a good time
> to polish the wording a bit while we are touching the general
> vicinity of the code.
>
> How about saying something like:
>
>  * refs/heads/origin: fast forward to remote branch 'master' of ../git/
>    old..new = 1ad7a06..bc1a580
I like it.
Show 9 quoted lines
>
> > * refs/heads/pu: does not fast forward to remote branch 'pu' of ../git/;
> >   7c733a8...5faa935
> >   not updating.
> >   forcing update.
> >   committish: 5faa935
>
> This is even more confusing.  Perhaps we would want to have two
> cases, depending on --force (and +).

Sorry, it was from two copy'n'paste. I did it in a new repository (without the +), then it stoped at this point (I suppose to force the user to solve the problem). Then I put the + and did the copy'n'paste again without deleting this extra line.

>
>  * refs/heads/pu: does not fast forward to remote branch 'pu' of ../git/;
>    but forcing update anyway.  old...new = 7c733a8...5faa935
With the old...new in a new line?
So at the end, something like this output?
$ git fetch -v   # the committish lines for the -v.
* refs/heads/origin: fast forward to remote branch 'master' of ../git/
 old..new: 1ad7a06..bc1a580
* refs/heads/pu: does not fast forward to remote branch 'pu' of ../git/
 old...new: 7c733a8...5faa935
 forcing update.
* refs/heads/next: same as remote branch 'origin/next' of ../git/
 committish: ce47b9f
...
* refs/tags/v1.4.2-rc4: storing tag 'v1.4.2-rc4' of ../git/
 committish: 8c7a107
$ git fetch -v origin refs/heads/master
* committish: 695dffe
 branch 'master' of ../git/
Santi
Previous: Junio C HamanoNext: Junio C Hamano
Message 8 of 12 in “fetch & co: misc output cleanup”
  1. 0/5 fetch & co: misc output cleanupSanti Béjar, Sep 29, 2006
  2. 1/5 fetch: Reset remote refs list each time fetch_main is calledSanti Béjar, Sep 29, 2006
  3. 2/5 fetch & co: Use "hash1..hash2" instead of "from hash1 to hash2"Santi Béjar, Sep 29, 2006
  4. 3/5 fetch & co: Use short sha1 in the outputSanti Béjar, Sep 29, 2006
  5. 4/5 fetch: Add output for the not fast forward caseSanti Béjar, Sep 29, 2006
  6. 5/5 fetch: Clean outputSanti Béjar, Sep 29, 2006
  7. Junio C HamanoSep 30, 2006
  8. SantiSep 30, 2006
  9. Junio C HamanoSep 30, 2006
  10. A Large Angry SCMSep 29, 2006
  11. SantiSep 29, 2006
  12. Junio C HamanoSep 29, 2006

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.