All of lore.kernel.org
 help / color / mirror / Atom feed
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:13:32 -0700	[thread overview]
Message-ID: <20189.1242278012@relay.known.net> (raw)
In-Reply-To: <32541b130905132158s44cc5b19n974901c05cf025b2@mail.gmail.com>

Avery Pennarun <apenwarr@gmail.com> wrote:

>> On Thu, May 14, 2009 at 12:42 AM, layer <layer@known.net> wrote:
>> > after the push, I still see the names of the files I pushed because I
>> > haven't updated origin/master yet, with a fetch.  Of course, a "git
>> > pull" would do it, but I don't want to do that, because I might be
>> > using something other than `origin' and I don't want anything but the
>> > single branch.
>> >
>> > So, I naively thought that
>> >
>> >  git fetch origin master
>> >
>> > would do the trick, but after that command the git diff above still
>> > shows the same files.
>> 
>> Short answer:
>> 
>>    git fetch origin
>> 
>> However, 'git push origin master' should update origin/master
>> automatically, at least in relatively recent git versions.  It's
>> rather weird if that didn't happen.

I decided to attempt cleanup myself:

  $ mv .git/refs/heads/origin/ git.refs.heads.origin
  $ git diff origin/master..master
  diff --git a/ChangeLog b/ChangeLog
  index f7b4551..f2200a0 100644
  --- a/ChangeLog
  +++ b/ChangeLog
  ...

OK, back to normal.

  $ git fetch origin
  From git:/repo/git/acl
     4be7cc8..28f0f4f  master     -> origin/master
  $ git diff origin/master..master
  $ 


I _swear_ I tried that.  <sigh>  Sorry to trouble everyone, and thanks
Avery.  Appreciated.

Kevin

  parent reply	other threads:[~2009-05-14  5:13 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 [this message]
2009-05-14  5:21   ` layer
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=20189.1242278012@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.