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

Re: Checking for fast-forward

From
LGLee Griffiths <poddster@gmail.com>
Date
Jul 8, 2009, 17:36 UTC
Message-ID
<ca4f67be0907081036j38724491n6c4c0e9aa995ee51@mail.gmail.com>
In-Reply-To
<4A530594.20100@drmicha.warpmail.net>
Thanks for the answers :)
After seeing that git push skips the packing (and potentially other
things) when doing a dry run, and given that:
	git push --dry-run
takes 1.5s on average and that:
	git fetch
	git rev-list master..remotes/origin/master
OR
	git ls-remote origin refs/remotes/origin/master

take 4s on average, I think I'll stick with the dry-run & checking for exception method.

Thanks though :)
2009/7/7 Michael J Gruber <git@drmicha.warpmail.net>:
> If $(git rev-list bar..remotes/origin/foo) is empty then the branch foo
> in the remote repo can be fast-forwarded to bar.
Previous: Michael J Gruber
Message 5 of 5 in “Re: Checking for fast-forward”
  1. Florian MicklerJul 6, 2009
  2. Michael J GruberJul 7, 2009
  3. Florian MicklerJul 7, 2009
  4. Michael J GruberJul 7, 2009
  5. Lee GriffithsJul 8, 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.