From: Jeff Garzik <jeff@garzik.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Losing branches (whee, data loss)
Date: Wed, 16 May 2007 02:40:09 -0400 [thread overview]
Message-ID: <464AA749.90101@garzik.org> (raw)
In-Reply-To: <7vtzudfgam.fsf@assigned-by-dhcp.cox.net>
Junio C Hamano wrote:
> Jeff Garzik <jeff@garzik.org> writes:
>
>> 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
>
> Sorry to hear that.
>
> We used to have a problem with "branch -m" when you did not have
> a .git/config file (or it was unwritable). I think 1.5.0.X
> series and 1.5.1 release had this bug; 1.5.1.1 and later should
> have the appropriate fix.
Using the latest version from Fedora Extras: git-core-1.5.0.6-1.fc6
> Was this really a "whee, data loss", I wonder...?
The branches definitely went away. The sha1-indexed commits are
probably still there...
Jeff
prev parent 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
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 [this message]
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=464AA749.90101@garzik.org \
--to=jeff@garzik.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.