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

hooks/post-receive-email bug?

From
Marc Branchaud <marcnarc@xiplink.com>
Date
Jun 17, 2009, 22:21 UTC
Message-ID
<4A396C6E.2050600@xiplink.com>
Hi all,
We currently have two main development branches: master and release.  These branches exist on our shared git server.  I had to make a change in both branches, so I made a topic branch off of their merge-base and did the work:
  o--o--A--B--C		<-- origin/master
     |\
     | X--Y		<-- origin/release
      \
       1--2--3		<-- topic
I then merged topic into both master and release.  The merges were clean:
  o--o--A--B--C---D	<-- master
     |\           |
     | X--Y----Z /	<-- release
      \       / /
       1--2--3--	<-- topic
Then I did
	git push origin
to push matching refspecs to the origin repo.
port-receive-email sent two messages for that push, one for each branch.  Each message showed that commits 1, 2 and 3 were applied to the appropriate branch:
	The branch, release has been updated
	       via  hash for Z (commit)
	       via  hash for 3 (commit)
	       via  hash for 2 (commit)
	       via  hash for 1 (commit)
	      from  hash for Y (commit)
However, the details of the topic commits were missing from both messages.  Instead, both only contained the details of the merge commits D and Z.
I was expecting at least one of the messages to have the details of commits 1, 2 and 3.  Was I wrong to expect that?
Thanks,
		M.
Next: Marc Branchaud
Message 1 of 4 in “hooks/post-receive-email bug?”
  1. Marc BranchaudJun 17, 2009
  2. Marc BranchaudJul 6, 2009
  3. Michael J GruberJul 7, 2009
  4. Marc BranchaudJul 7, 2009

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.