From: Andreas Schwab <schwab@linux-m68k.org>
To: Phil Hord <hordp@cisco.com>
Cc: Eric Blake <eblake@redhat.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: git push vs. slow connection times - local commit resolution is too late
Date: Sat, 16 Jul 2011 14:52:06 +0200 [thread overview]
Message-ID: <m2oc0uz8uh.fsf@igel.home> (raw)
In-Reply-To: <4E2115D5.4010002@cisco.com> (Phil Hord's message of "Sat, 16 Jul 2011 00:38:45 -0400")
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."
next prev parent reply other threads:[~2011-07-16 12:53 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-14 13:22 git push vs. slow connection times - local commit resolution is too late Eric Blake
2011-07-16 4:38 ` Phil Hord
2011-07-16 12:52 ` Andreas Schwab [this message]
2011-07-17 19:46 ` Phil Hord
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m2oc0uz8uh.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=eblake@redhat.com \
--cc=git@vger.kernel.org \
--cc=hordp@cisco.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).