From: "Lars Hjemli" <hjemli@gmail.com>
To: "Jeff Garzik" <jeff@garzik.org>
Cc: "Git Mailing List" <git@vger.kernel.org>
Subject: Re: Losing branches (whee, data loss)
Date: Wed, 16 May 2007 07:48:07 +0200 [thread overview]
Message-ID: <8c5c35580705152248w254e4201w65da1e1ad229f6ee@mail.gmail.com> (raw)
In-Reply-To: <464A940C.3080906@garzik.org>
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@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?
--
larsh
next prev parent reply other threads:[~2007-05-16 5:48 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 [this message]
2007-05-16 5:54 ` Jeff Garzik
2007-05-16 6:14 ` Jan Hudec
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=8c5c35580705152248w254e4201w65da1e1ad229f6ee@mail.gmail.com \
--to=hjemli@gmail.com \
--cc=git@vger.kernel.org \
--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).