From: layer <layer@known.net>
To: Avery Pennarun <apenwarr@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: how to update origin/<branch> after a push to origin <branch>?
Date: Wed, 13 May 2009 22:21:09 -0700 [thread overview]
Message-ID: <20329.1242278469@relay.known.net> (raw)
In-Reply-To: <32541b130905132158s44cc5b19n974901c05cf025b2@mail.gmail.com>
Avery Pennarun <apenwarr@gmail.com> wrote:
>> Short answer:
>>
>> git fetch origin
I wasn't doing exactly this, but I was doing the equivalent of
git fetch $(git config --get remote.origin.url)
Why would these be different?
Kevin
next prev parent reply other threads:[~2009-05-14 5:21 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-14 4:42 how to update origin/<branch> after a push to origin <branch>? layer
2009-05-14 4:58 ` Avery Pennarun
2009-05-14 5:01 ` layer
2009-05-14 5:13 ` layer
2009-05-14 5:21 ` layer [this message]
2009-05-14 5:29 ` Avery Pennarun
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=20329.1242278469@relay.known.net \
--to=layer@known.net \
--cc=apenwarr@gmail.com \
--cc=git@vger.kernel.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