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

Re: [PATCH 0/2] log/ format-patch improvements

From
Ramkumar Ramachandra <artagnon@gmail.com>
Date
Aug 26, 2010, 05:34 UTC
Message-ID
<20100826053439.GB9407@kytes>
In-Reply-To
<20100825205416.GB2319@burratino>
Hi Jonathan and Junio,
Junio C Hamano writes:
> I am not very impressed by the counting.  It probably makes more sense to
> count only what we are actually going to process and emit, i.e. always use
> no-merges (do we even support format-patch on a merge?).  

Frankly, I think the patch looks like an ugly hack myself. No, format-patch doesn't support merge commits at all.

Jonathan Nieder writes:
Show 11 quoted lines
> Ramkumar Ramachandra wrote:
> > Ramkumar Ramachandra writes:
> 
> >> The second patch clarifies the meaning of the `-<n>` option. We should
> >> also probably force the mutual exclusivity of `-<n>` and <revision
> >> range> to avoid confusion.
> [...]
> > Do you see value in this patch or is it just unnecessary baggage?
> 
> I see value in avoiding confusion.  Maybe one solution would be to make
> format-patch use --no-merges by default.

Good idea. I'll write a patch. Do we also want people to be able to turn off `--no-merges`? If so, how?

-- Ram
Previous: Jonathan NiederNext: Jonathan Nieder
Message 6 of 11 in “log/ format-patch improvements”
  1. 0/2 log/ format-patch improvementsRamkumar Ramachandra, Aug 21, 2010
  2. 1/2 git-format-patch: Print a diagnostic message when ignoring commitsRamkumar Ramachandra, Aug 21, 2010
  3. 2/2 log: Improve description of '-<n>' option in documentationRamkumar Ramachandra, Aug 21, 2010
  4. Ramkumar RamachandraAug 25, 2010
  5. Jonathan NiederAug 25, 2010
  6. Ramkumar RamachandraAug 26, 2010
  7. Jonathan NiederAug 26, 2010
  8. Thomas RastAug 26, 2010
  9. Junio C HamanoAug 26, 2010
  10. Ramkumar RamachandraAug 26, 2010
  11. Junio C HamanoAug 25, 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.