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

Feature request: git-pull -e/--edit

From
Llinux@horizon.com <linux@horizon.com>
Date
Nov 19, 2006, 21:26 UTC
Message-ID
<20061119212611.13038.qmail@science.horizon.com>

The last end-user use I can think of for git-merge instead of git-pull is providing a custom commit message.

Would it be possible to add -m and -e options to git-pull?

The problem I can see is that the latter would have to be added to git-merge, and the guts there are a bit intricate; it uses git-commit-tree directly rather than git-commit, so I can't just pass through the arguments.

Assuming it's just as much of a pain for someone else, would it still be worth the effort? Can git-merge be cleaned up?

The manual option is to use "git merge --no-commit" and then supply the arguments to git-commit in the usual way.

But I notice that --no-commit actually changes git's merging technique. If it's specified, the trivial in-index merge doesn't appear to be attempted. I don't think it makes a huge difference,

Next: Junio C Hamano
Message 1 of 7 in “Feature request: git-pull -e/--edit”
  1. linux@horizon.comNov 19, 2006
  2. Junio C HamanoNov 20, 2006
  3. linux@horizon.comNov 20, 2006
  4. Junio C HamanoNov 20, 2006
  5. Jakub NarebskiNov 20, 2006
  6. git-merge: make it usable as the first class UIJunio C Hamano, Nov 20, 2006
  7. Junio C HamanoNov 22, 2006

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.