git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Phil Hord <hordp@cisco.com>
To: Andreas Schwab <schwab@linux-m68k.org>
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: Sun, 17 Jul 2011 15:46:28 -0400	[thread overview]
Message-ID: <4E233C14.6080309@cisco.com> (raw)
In-Reply-To: <m2oc0uz8uh.fsf@igel.home>

Andreas Schwab helpfully chimed in
 > 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?

Yes, I do. :-) But I don't use it enough to remember it, and the man 
pages are not cross-referenced well enough for me.  So I shrugged.

Thanks for helping me out.

Phil

      reply	other threads:[~2011-07-17 19:46 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
2011-07-17 19:46     ` Phil Hord [this message]

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=4E233C14.6080309@cisco.com \
    --to=hordp@cisco.com \
    --cc=eblake@redhat.com \
    --cc=git@vger.kernel.org \
    --cc=schwab@linux-m68k.org \
    /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).