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

Re: wishlist bugreport: make limit configurable for do_fmt_merge_msg (merge.log)

From
Johannes Sixt <j.sixt@viscovery.net>
Date
Aug 20, 2010, 09:10 UTC
Message-ID
<4C6E468F.3000800@viscovery.net>
In-Reply-To
<20100820081641.GA32127@burratino>
Am 8/20/2010 10:16, schrieb Jonathan Nieder:
> This also provides --log-limit=0 / "[merge] loglimit = 0" to not limit
> the number of commits summarized at all, which I would expect to
...
Show 5 quoted lines
>  [verse]
> -'git fmt-merge-msg' [--log | --no-log] <$GIT_DIR/FETCH_HEAD
> -'git fmt-merge-msg' [--log | --no-log] -F <file>
> +'git fmt-merge-msg' [--log | --no-log] [--log-limit=<n>] <$GIT_DIR/FETCH_HEAD
> +'git fmt-merge-msg' [--log | --no-log] [--log-limit=<n>] -F <file>
Do we need --log-limit? Why not just --log=42 and --no-log equals --log=0?
Ditto for the config option:
  merge.log=42
  merge.log=0
and for backwards compatibility:
  merge.log=false  ===  merge.log=0
  merge.log=true   ===  merge.log=20
-- Hannes
Previous: Ramkumar RamachandraNext: Ramkumar Ramachandra
Message 5 of 7 in “wishlist bugreport: make limit configurable for do_fmt_merge_msg (merge.log)”
  1. Yaroslav HalchenkoAug 20, 2010
  2. Ramkumar RamachandraAug 20, 2010
  3. Jonathan NiederAug 20, 2010
  4. Ramkumar RamachandraAug 20, 2010
  5. Johannes SixtAug 20, 2010
  6. Ramkumar RamachandraAug 20, 2010
  7. Johannes SixtAug 20, 2010

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.