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

[PATCH 0/2] teach git pull to handle --log=<n>

From
Paul Tan <pyokagan@gmail.com>
Date
May 13, 2015, 09:17 UTC
Message-ID
<1431508661-21729-1-git-send-email-pyokagan@gmail.com>

Since efb779f (merge, pull: add '--(no-)log' command line option, 2008-04-06) git-pull supported the (--no-)log switch and would pass it to git-merge.

96e9420 (merge: Make '--log' an integer option for number of shortlog entries, 2010-09-08) implemented support for the --log=<n> switch, which would explicitly set the number of shortlog entries. However, git-pull does not recognize this option, and will instead pass it to git-fetch, leading to "unknown option" errors.

This patch series implements a failing test that demonstrates the above, and teaches git-pull to handle the switch --log=<n>.

Paul Tan (2):
  t5524: test --log=1 limits shortlog length
  pull: handle --log=<n>
 git-pull.sh         |  4 ++--
 t/t5524-pull-msg.sh | 17 +++++++++++++++++
 2 files changed, 19 insertions(+), 2 deletions(-)
-- 
2.1.4
Next: Paul Tan
Message 1 of 9 in “teach git pull to handle --log=<n>”
  1. 0/2 teach git pull to handle --log=<n>Paul Tan, May 13, 2015
  2. 1/2 t5524: test --log=1 limits shortlog lengthPaul Tan, May 13, 2015
  3. 2/2 pull: handle --log=<n>Paul Tan, May 13, 2015
  4. Matthieu MoyMay 13, 2015
  5. Johannes SchindelinMay 13, 2015
  6. Matthieu MoyMay 13, 2015
  7. Matthieu MoyMay 13, 2015
  8. Junio C HamanoMay 14, 2015
  9. Paul TanMay 15, 2015

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.