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

Re: git push vs. slow connection times - local commit resolution is too late

From
Andreas Schwab <schwab@linux-m68k.org>
Date
Jul 16, 2011, 12:52 UTC
Message-ID
<m2oc0uz8uh.fsf@igel.home>
In-Reply-To
<4E2115D5.4010002@cisco.com>
Phil Hord <hordp@cisco.com> writes:
> I agree with your suggestion.  But as a quick fix, can you do this?
>   git push remote $(cat .git/HEAD):master
You mean $(git rev-parse HEAD), don't you?
Andreas.
-- 
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756  01D3 44D5 214B 8276 4ED5
"And now for something completely different."
Previous: Phil HordNext: Phil Hord
Message 3 of 4 in “git push vs. slow connection times - local commit resolution is too late”
  1. Eric BlakeJul 14, 2011
  2. Phil HordJul 16, 2011
  3. Andreas SchwabJul 16, 2011
  4. Phil HordJul 17, 2011

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.