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

Re: New ref generates 8MB mail message

From
Linus Torvalds <torvalds@osdl.org>
Date
Jan 18, 2006, 16:12 UTC
Message-ID
<Pine.LNX.4.64.0601180810330.3240@g5.osdl.org>
In-Reply-To
<20060118140907.GV19769@parisc-linux.org>
On Wed, 18 Jan 2006, Matthew Wilcox wrote:
> 
> Based on the idea that a new branch is probably a branch off master, and
> if it isn't, then at least sending a log vs master is better than a log
> vs the beginning of time, I propose this patch:

Actually, since the update hook _should_ be called before the ref has actually been updated, it's probably much better to instead of this:

> -	git-rev-list --pretty "$3"
> +	git-rev-list --pretty "$3" ^master
do something like this:
	git-rev-list --pretty "$3" $(git-rev-parse --not --all)

which basically says: show any commits that are in the new ref, but are not in _any_ other ref.

Untested, of course.
		Linus
Previous: Matthew WilcoxNext: Andreas Ericsson
Message 2 of 3 in “New ref generates 8MB mail message”
  1. Matthew WilcoxJan 18, 2006
  2. Linus TorvaldsJan 18, 2006
  3. Andreas EricssonJan 19, 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.