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

Re: [PATCH] request-pull: do not paginate output of git commands

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 1, 2009, 20:16 UTC
Message-ID
<7vy6r8f9aq.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20090701094029.GA22508@sepie.suse.cz>
Michal Marek <mmarek@suse.cz> writes:
> Good idea, but for completeness, it should be set before this command:
>     git log --max-count=1 --pretty='format:warn:   %h: %s' $headrev >&2
> (which should use tformat to get the newline right). So what about this
> one?
Good eyes.

The blamed commit for that new use of "log" is ff06c74 (Improve request-pull to handle non-rebased branches, 2007-05-01) itself, which did introduce the "define an empty PAGER to disable paging" trick, so this makes it doubly buggy (i.e. for forgetting GIT_PAGER trumps PAGER, and for introducing a use of log that is not covered by its own trick).

Thanks.
Previous: Michal Marek
Message 7 of 7 in “request-pull: do not paginate output of git commands”
  1. request-pull: do not paginate output of git commandsMichal Marek, Jun 30, 2009
  2. Junio C HamanoJun 30, 2009
  3. Junio C HamanoJun 30, 2009
  4. Michal MarekJun 30, 2009
  5. Junio C HamanoJun 30, 2009
  6. Michal MarekJul 1, 2009
  7. Junio C HamanoJul 1, 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.