git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Hudec <bulb@ucw.cz>
To: Jeff Garzik <jeff@garzik.org>
Cc: Lars Hjemli <hjemli@gmail.com>, Git Mailing List <git@vger.kernel.org>
Subject: Re: Losing branches (whee, data loss)
Date: Wed, 16 May 2007 08:14:49 +0200	[thread overview]
Message-ID: <20070516061449.GA25273@artax.karlin.mff.cuni.cz> (raw)
In-Reply-To: <464A9C9B.70904@garzik.org>

On Wed, May 16, 2007 at 01:54:35AM -0400, Jeff Garzik wrote:
> Lars Hjemli wrote:
> >On 5/16/07, Jeff Garzik <jeff@garzik.org> wrote:
> >>[jgarzik@pretzel libata-dev]$ git branch -m upstream-fixes tmp
> >>error: Could not open config file!
> >>fatal: Branch rename failed
> >
> >This should have been fixed in v1.5.1.1, what version do you run?
> 
> [jgarzik@core ~]$ rpm -q git-core
> git-core-1.5.0.6-1.fc6
> 
> 
> >>[jgarzik@pretzel libata-dev]$ git-branch -m upstream-fixes tmp
> >>fatal: A branch named 'tmp' already exists.
> >>
> >>[jgarzik@pretzel libata-dev]$ git branch -D tmp
> >>Deleted branch tmp.
> >
> >Could you try to run "git log -g" and see if it finds your lost branch?
> 
> Doesn't seem to..

And does the .git/logs/refs/heads/upstream-fixes still exist?

If it does, than revspec upstream-fixes@{1} would still work, so you can
check it out, re-create the branch and update the ref (git update-ref).

If it does not, as last resort you'd have to git fsck --unreachable
(this gives you all things that are not reachable from any ref), filter
out only commit objects and than remember which one should have been on
that branch after reading it's log, date and changes.

--------------------------------------------------------------------------------
                  				- Jan Hudec `Bulb' <bulb@ucw.cz>

  reply	other threads:[~2007-05-16  6:40 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-16  5:18 Losing branches (whee, data loss) Jeff Garzik
2007-05-16  5:48 ` Lars Hjemli
2007-05-16  5:54   ` Jeff Garzik
2007-05-16  6:14     ` Jan Hudec [this message]
2007-05-16  6:40       ` Jeff Garzik
2007-05-16  6:43         ` Junio C Hamano
2007-05-16  7:10         ` Lars Hjemli
2007-05-16  7:36           ` Junio C Hamano
2007-05-16  6:12 ` Junio C Hamano
2007-05-16  6:40   ` Jeff Garzik

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=20070516061449.GA25273@artax.karlin.mff.cuni.cz \
    --to=bulb@ucw.cz \
    --cc=git@vger.kernel.org \
    --cc=hjemli@gmail.com \
    --cc=jeff@garzik.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).