From: Jeff Garzik <jeff@garzik.org>
To: Git Mailing List <git@vger.kernel.org>
Subject: Losing branches (whee, data loss)
Date: Wed, 16 May 2007 01:18:04 -0400 [thread overview]
Message-ID: <464A940C.3080906@garzik.org> (raw)
Grumble!
When all this started, the branch 'upstream-fixes' exists, and branch
'tmp' does not exist. This is my local clone of
git://git.kernel.org/pub/scm/linux/kernel/git/jgarzik/libata-dev.git
[jgarzik@pretzel libata-dev]$ git branch -m upstream-fixes tmp
error: Could not open config file!
fatal: Branch rename failed
[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.
[jgarzik@pretzel libata-dev]$ git-branch -m upstream-fixes tmp
error: refname refs/heads/upstream-fixes not found
fatal: Branch rename failed
next reply other threads:[~2007-05-16 5:18 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-16 5:18 Jeff Garzik [this message]
2007-05-16 5:48 ` Losing branches (whee, data loss) Lars Hjemli
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=464A940C.3080906@garzik.org \
--to=jeff@garzik.org \
--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 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).