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

Re: [PATCH] Add script for patch submission via e-mail.

From
Junio C Hamano <junkio@cox.net>
Date
Jul 5, 2005, 15:20 UTC
Message-ID
<7vekadfff6.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20050705093441.GD6191@pasky.ji.cz>
>>>>> "PB" == Petr Baudis <pasky@suse.cz> writes:
PB> Any reason why this was not applied? It appears kind of cool.

FYI, the one in <7vll4s47p3.fsf_-_@assigned-by-dhcp.cox.net> is newer than what you quoted.

One thing _I_ am unhappy about what it does is that it does not try to be intelligent about merges (I haven't tried the script on a merged head myself).

When you think about "project lead" vs "individual developer" modes of operation, the latter is primarily "keep rebasing commits in my fork and re-throwing them upstream until some of them stick", so not supporting merges specially would not be so big a flaw. However, at least it should use --merge-order to get the epochs decomposed right, in order to produce anything remotely useful when dealing with a merged head.

Previous: Jon SeymourNext: Jon Seymour
Message 4 of 6 in “Add script for patch submission via e-mail.”
  1. Add script for patch submission via e-mail.Junio C Hamano, Jun 11, 2005
  2. Petr BaudisJul 5, 2005
  3. Jon SeymourJul 5, 2005
  4. Junio C HamanoJul 5, 2005
  5. Jon SeymourJul 5, 2005
  6. Add script for patch submission via e-mail.Junio C Hamano, Jul 5, 2005

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.