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

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

From
Junio C Hamano <junkio@cox.net>
Date
Nov 22, 2006, 23:02 UTC
Message-ID
<7v3b8bozje.fsf@assigned-by-dhcp.cox.net>
In-Reply-To
<20061119212611.13038.qmail@science.horizon.com>
linux@horizon.com writes:
> 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,
> but is any difference desirable?

This was done in response to a specific request from the list but I do not remember the details. If I were to research the background I would

 (1) first, look at the authordate of the commit that introduced
     the change.  For this, I would most likely use:
	git log -p -S--no-commit -- git-pull.sh
 (2) go back to the list archive and find the thread that
     predates that commit by a few days.
Previous: Junio C Hamano
Message 7 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.