From: tom fogal <tfogal@sci.utah.edu>
To: git@vger.kernel.org
Subject: rebuild repo from data, packfiles?
Date: Sat, 20 Nov 2010 15:54:16 -0700 [thread overview]
Message-ID: <auto-000024044659@sci.utah.edu> (raw)
Long story short, I lost some metadata in a repo I've got. However,
my entire .git/objects/ && subdirs is intact, so I'm hopeful my data's
still accessible in some form.
I'm trying to piece together the git metadata that goes in .git (no
subdirs) based on what I've got in other repos && what fails when I
strace git, in hopes I can rebuild my reflog to grab all the work
I only had locally. Currently I can't `log' or `reflog' or really
anything, because git thinks this directory isn't a git repo.
I'm curious if there's ideas out there for rebuilding my repo based on
the repo's data. Is there a command I could point at .git/objects and
have it repopulate the repo?
Thanks,
-tom
next reply other threads:[~2010-11-20 23:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-20 22:54 tom fogal [this message]
2010-11-21 0:16 ` rebuild repo from data, packfiles? Jonathan Nieder
2010-11-21 2:44 ` tom fogal
2010-11-21 3:27 ` Jonathan Nieder
2010-11-21 3:55 ` tom fogal
2010-11-21 4:19 ` Jonathan Nieder
2010-11-21 19:51 ` tom fogal
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=auto-000024044659@sci.utah.edu \
--to=tfogal@sci.utah.edu \
--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).