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

Re: [PATCH] Added hook in git-receive-pack

From
JWJosef Weidendorfer <josef.weidendorfer@gmx.de>
Date
Aug 13, 2005, 18:31 UTC
Message-ID
<200508132031.27668.Josef.Weidendorfer@gmx.de>
In-Reply-To
<200507312117.43957.Josef.Weidendorfer@gmx.de>
On Sunday 31 July 2005 21:17, Josef Weidendorfer wrote:
> Added hook in git-receive-pack

Regarding the update hook: In this script, it would be nice to be able to distinguish rebasing/forced setting of a head from a regular fast forwarding. In the first case, I do not want to potentially send a list of all commits starting from project root, which currently can happen.

A solution would be to call the hook simply with
	update refname new_sha1
if this is not a fast forward.
The question is if there is a use case for the script to get the old_sha1 even 
in a rebase situation. So another option would be to call the script with
	update action refname old_sha1 new_sha1
with action being "fastforward" or "forcedrebase" or similar.

Or is there already an easy way to detect the fast-forward situation in the script?

Josef
Previous: Junio C HamanoNext: Junio C Hamano
Message 13 of 15 in “Added hook in git-receive-pack”
  1. Added hook in git-receive-packJosef Weidendorfer, Jul 31, 2005
  2. Linus TorvaldsJul 31, 2005
  3. Junio C HamanoJul 31, 2005
  4. Linus TorvaldsJul 31, 2005
  5. Junio C HamanoJul 31, 2005
  6. Johannes SchindelinJul 31, 2005
  7. Linus TorvaldsJul 31, 2005
  8. Junio C HamanoAug 1, 2005
  9. Linus TorvaldsAug 1, 2005
  10. Junio C HamanoJul 31, 2005
  11. Josef WeidendorferJul 31, 2005
  12. Junio C HamanoAug 1, 2005
  13. Josef WeidendorferAug 13, 2005
  14. Junio C HamanoAug 13, 2005
  15. Josef WeidendorferAug 13, 2005

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.