Re: Losing branches (whee, data loss)

Jeff Garzik [off-list ref] 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.

Was this really a "whee, data loss", I wonder...?

Junio C Hamano wrote:

Jeff Garzik [off-list ref] writes:

quoted

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