git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Franz Liedke" <franz@develophp.org>
To: "Sverre Rabbelier" <srabbelier@gmail.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: [Support] Branch pointer does not move
Date: Mon, 14 Mar 2011 16:18:39 +0100	[thread overview]
Message-ID: <op.vsb95dilbl4hj1@metalltrottel.fritz.box> (raw)
In-Reply-To: <AANLkTik5MGyw_6vnT8055Yap3Ca1pDQYpJ_RXiZQbwA4@mail.gmail.com>

Hey,

thanks for your response.

"git status" and "git branch" both tell me I'm on my feature branch.

.git/packed-refs and .git/info/refs are both not updated.
.git/refs/heads/168-users-mass-edit is updated.

On Mon, 14 Mar 2011 16:09:39 +0100, Sverre Rabbelier  
<srabbelier@gmail.com> wrote:

> Heya,
>
> On Mon, Mar 14, 2011 at 14:18, Franz Liedke <franz@develophp.org> wrote:
>> I am currently having some trouble with a local Git branch.
>> It seems the branch pointer is not updated when I make new commits to  
>> that
>> particular branch.
>
> You might not be on any branch/the branch you expect. What does 'git
> status' and 'git branch ' say?
>


-- 
Using Opera's revolutionary email client: http://www.opera.com/mail/

  reply	other threads:[~2011-03-14 15:17 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-03-14 13:18 [Support] Branch pointer does not move Franz Liedke
2011-03-14 15:09 ` Sverre Rabbelier
2011-03-14 15:18   ` Franz Liedke [this message]
2011-03-14 15:19     ` Sverre Rabbelier
2011-03-14 15:24       ` Franz Liedke
2011-03-14 15:24         ` Sverre Rabbelier
2011-03-14 15:48         ` Michael J Gruber
2011-03-14 16:14           ` Franz Liedke
2011-03-14 16:29             ` Michael J Gruber
2011-03-14 16:44               ` Franz Liedke
2011-03-15 15:27                 ` Michael J Gruber

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=op.vsb95dilbl4hj1@metalltrottel.fritz.box \
    --to=franz@develophp.org \
    --cc=git@vger.kernel.org \
    --cc=srabbelier@gmail.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).