From: Jeff Garzik <jeff@garzik.org>
To: Jan Hudec <bulb@ucw.cz>
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 02:40:51 -0400 [thread overview]
Message-ID: <464AA773.3090808@garzik.org> (raw)
In-Reply-To: <20070516061449.GA25273@artax.karlin.mff.cuni.cz>
Jan Hudec wrote:
> And does the .git/logs/refs/heads/upstream-fixes still exist?
Nope.
> 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.
Yeah, that will probably recover it. I wound up digging the emails out
of the trash bin, and applying them again.
Jeff
next prev parent reply other threads:[~2007-05-16 6:41 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 [this message]
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=464AA773.3090808@garzik.org \
--to=jeff@garzik.org \
--cc=bulb@ucw.cz \
--cc=git@vger.kernel.org \
--cc=hjemli@gmail.com \
/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).