git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Franz Liedke <franz@develophp.org>
Cc: Sverre Rabbelier <srabbelier@gmail.com>, git@vger.kernel.org
Subject: Re: [Support] Branch pointer does not move
Date: Mon, 14 Mar 2011 17:29:43 +0100	[thread overview]
Message-ID: <4D7E4277.8040202@drmicha.warpmail.net> (raw)
In-Reply-To: <op.vsccqtbobl4hj1@metalltrottel.fritz.box>

Franz Liedke venit, vidit, dixit 14.03.2011 17:14:
> Hey Michael,
> 
> in fact, I have been making commits both from the command line and from  
> SmartGit from time to time, and yes, they were both running.
> This has never been the problem before.
> 

I don't know how smartgit reacts when you switch the branch in git while
smartgit is running, for example.

> I ran some sort of cleanup tool yesterday, possibly about the time when  
> the problem started (I only noticed it today). Something along the lines  
> of 'git gc' maybe, if I remember correctly. Could that be the cause?

git gc does not do any evil as long as you're not accessing the repo
with another client at the same time.

So, have you lost any commits? Maybe something like

git log --graph --abbrev-commit --pretty=oneline --decorate --all

will give you a clearer picture of where your commits went. If they're
not there then inspecting the reflog of HEAD may help:

git log -g --abbrev-commit --pretty=oneline --decorate HEAD

Michael

  reply	other threads:[~2011-03-14 16:33 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
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 [this message]
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=4D7E4277.8040202@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=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).