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

Re: [PATCH] Implement rebase -q to fix pull --rebase -q

From
Junio C Hamano <gitster@pobox.com>
Date
Dec 3, 2008, 07:54 UTC
Message-ID
<7vej0pheww.fsf@gitster.siamese.dyndns.org>
In-Reply-To
<1228277212-5917-1-git-send-email-tuncer.ayaz@gmail.com>
Tuncer Ayaz <tuncer.ayaz@gmail.com> writes:
> This is needed on top of the fetch/pull -q/-v changes
> to make
> $ git pull --rebase -q
> as quiet as expected.

I am not sure if this is worth it, in the sense that it is not really quiet enough (iow, it is not what I expect even though you claim "as expected" here), and in another sense that making it really quiet may not be what we want anyway.

How are you dealing with messages from the actual replaying of each local commit on top of what is fetched? In order to be able to tell where you are when one of them fail in conflicts, you cannot stay silent while doing so.

Previous: Tuncer AyazNext: Tuncer Ayaz
Message 3 of 8 in “Implement rebase -q to fix pull --rebase -q”
  1. Implement rebase -q to fix pull --rebase -qTuncer Ayaz, Dec 3, 2008
  2. Tuncer AyazDec 3, 2008
  3. Junio C HamanoDec 3, 2008
  4. Tuncer AyazDec 3, 2008
  5. Junio C HamanoDec 3, 2008
  6. Tuncer AyazDec 3, 2008
  7. Junio C HamanoDec 3, 2008
  8. Tuncer AyazDec 3, 2008

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.