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

Re: [PATCH 1/3] doc: merge-tree: provide a commit message

From
KHKristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
Date
Oct 7, 2024, 12:02 UTC
Message-ID
<b41ce281-d3b8-43c3-8b27-f5dc59601ca7@app.fastmail.com>
In-Reply-To
<fef203471f4492af1468a0c91088324c394effd5.1728298931.git.code@khaugsbakk.name>
On Mon, Oct 7, 2024, at 13:10, Kristoffer Haugsbakk wrote:
> From: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>
>
> From: Kristoffer Haugsbakk <code@khaugsbakk.name>

I think these got double upped since I used `--from` in format-patch. Then I used send-email. format-patch warns against that:

  “ Note that this option is only useful if you are actually sending the
    emails and want to identify yourself as the sender, but
    retain the original author (and git am will correctly pick up
    the in-body header). Note also that git send-email already
    handles this transformation for you, and this option should
    not be used if you are feeding the result to git send-email.
So under the normal use I guess:

• You have someone else’s patches • send-email sees that you are not that person (because of your config) • It puts the From in the message body (it just works)

But that wasn’t the case for me since my ident is still the same as the author.

That went over my head before I sent.
-- 
Kristoffer Haugsbakk
Previous: Kristoffer HaugsbakkNext: Elijah Newren
Message 3 of 27 in “doc: merge-tree: improve the script example”
  1. 0/3 doc: merge-tree: improve the script exampleKristoffer Haugsbakk, Oct 7, 2024
  2. 1/3 doc: merge-tree: provide a commit messageKristoffer Haugsbakk, Oct 7, 2024
  3. Kristoffer HaugsbakkOct 7, 2024
  4. Elijah NewrenOct 7, 2024
  5. Kristoffer HaugsbakkOct 7, 2024
  6. 2/3 doc: merge-tree: use lower-case variablesKristoffer Haugsbakk, Oct 7, 2024
  7. Phillip WoodOct 7, 2024
  8. Elijah NewrenOct 7, 2024
  9. 3/3 doc: merge-tree: use || directlyKristoffer Haugsbakk, Oct 7, 2024
  10. Elijah NewrenOct 7, 2024
  11. Kristoffer HaugsbakkOct 7, 2024
  12. Phillip WoodOct 7, 2024
  13. Kristoffer HaugsbakkOct 7, 2024
  14. 0/2 doc: merge-tree: improve the script exampleKristoffer Haugsbakk, Oct 8, 2024
  15. 1/2 doc: merge-tree: provide a commit messageKristoffer Haugsbakk, Oct 8, 2024
  16. Junio C HamanoOct 8, 2024
  17. Kristoffer HaugsbakkOct 8, 2024
  18. Kristoffer HaugsbakkOct 9, 2024
  19. Junio C HamanoOct 9, 2024
  20. Andreas SchwabOct 9, 2024
  21. 2/2 doc: merge-tree: use || directlyKristoffer Haugsbakk, Oct 8, 2024
  22. Junio C HamanoOct 8, 2024
  23. Kristoffer HaugsbakkOct 8, 2024
  24. 0/1 doc: merge-tree: improve the script exampleKristoffer Haugsbakk, Oct 9, 2024
  25. 1/1 doc: merge-tree: improve example scriptKristoffer Haugsbakk, Oct 9, 2024
  26. Elijah NewrenOct 9, 2024
  27. Junio C HamanoOct 10, 2024

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.