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

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

From
Junio C Hamano <gitster@pobox.com>
Date
Aug 26, 2010, 15:37 UTC
Message-ID
<7vk4ndo05p.fsf@alter.siamese.dyndns.org>
In-Reply-To
<20100826054659.GC9708@burratino>
Jonathan Nieder <jrnieder@gmail.com> writes:
Show 10 quoted lines
> Ramkumar Ramachandra wrote:
> ...
>> Good idea. I'll write a patch. Do we also want people to be able to
>> turn off `--no-merges`?
>
> I don't see a need for it.
>
> However, if you can think of good names for --undo-no-merges and
> --undo-merges options to "git log", that might be a nice independent
> change for the revision option parser.

Wait a bit. How would you represent a merge in a patch form that can be read by "git apply" (and "patch") in the first place?

Previous: Thomas RastNext: Ramkumar Ramachandra
Message 9 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.