From: Dennis Schridde <devurandom@gmx.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Multiple user questions
Date: Fri, 6 Jun 2008 22:47:39 +0200 [thread overview]
Message-ID: <200806062247.42074.devurandom@gmx.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 754 bytes --]
I just ran into a lost stash again and thus would like to get an answer to
this question, which was forgotten last time:
(lost-found is really growing in a pace it will take me very long to find my
lost stash.)
5) fsck --full --lost-found shows me a lot of "dangling commit". I would like
to clean them up. prune did only remove "dangling tree" and blobs.
(Reason: Last time I droped a stash accidently, I was able to find it in that
list. I will not be able to do this again if it continues to grow at that
rate.)
How can I do that?
Further fsck --full --unreachable also shows a lot of unreachable things
(commits, trees, blobs). Can that be cleaned up as well?
Greetings,
Dennis
Again: Please CC me, as I am not subscribed.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 197 bytes --]
next reply other threads:[~2008-06-06 21:01 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-06 20:47 Dennis Schridde [this message]
2008-06-06 21:19 ` Multiple user questions Brandon Casey
2008-06-06 22:15 ` Dennis Schridde
-- strict thread matches above, loose matches on Subject: below --
2008-05-23 11:27 Dennis Schridde
2008-05-23 11:37 ` Dennis Schridde
2008-05-24 1:30 ` Jakub Narebski
2008-05-24 9:13 ` Dennis Schridde
2008-05-24 12:33 ` Jakub Narebski
2008-05-25 8:49 ` Dennis Schridde
2008-05-27 8:24 ` Jakub Narebski
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=200806062247.42074.devurandom@gmx.net \
--to=devurandom@gmx.net \
--cc=git@vger.kernel.org \
--cc=jnareb@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).