From: "Paolo Ciarrocchi" <paolo.ciarrocchi@gmail.com>
To: "Git Mailing List" <git@vger.kernel.org>
Cc: torvalds@osdl.org, "Alan Cox" <alan@lxorguk.ukuu.org.uk>
Subject: Re: Nasty git corruption problem
Date: Wed, 26 Jul 2006 17:57:03 +0200 [thread overview]
Message-ID: <4d8e3fd30607260857v17bde4afqbe68fde583d2f15f@mail.gmail.com> (raw)
In-Reply-To: <1153929715.13509.12.camel@localhost.localdomain>
Just added the git ML where you can have better support for this problem.
On 7/26/06, Alan Cox <alan@lxorguk.ukuu.org.uk> wrote:
> Just hit a real nasty, although I suspect its not a common case but it
> does seem to show a problem git has other version control systems don't
> (so far anyway)
>
> During a git rebase my machine crashed. Git claims that the rebase is
> complete but contains none of the outstanding 30 odd patches. There is
> no .dotest directory and git-fsck-objects produces some warnings about a
> few dangling objects, but these objects aren't the relevant ones (at
> least directly)
>
> CVS and SVN in crashes don't lose old stuff, though they are pretty good
> at losing the last commit or two. Git rebase appears to be able to lose
> two weeks of old changes even though they were stable on disk, which is
> not good at all.
>
> Doing
>
> for i in *; do (cd $i; for j in *; do git-unpack-file $i$j; done; );
> done
>
> shows that lots of the changes are still somewhere in the object tree
> but there seems to be no tool for fixing rather than moaning about
> objects dangling, and also no obvious way to fix it. Also curiously many
> of the objects appear linked somewhere but don't show up in the git-log
> for the afflicted branch at all.
>
>
>
>
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
>
--
Paolo
http://paolo.ciarrocchi.googlepages.com
http://picasaweb.google.com/paolo.ciarrocchi
next parent reply other threads:[~2006-07-26 15:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1153929715.13509.12.camel@localhost.localdomain>
2006-07-26 15:57 ` Paolo Ciarrocchi [this message]
2006-07-26 17:07 ` Nasty git corruption problem Linus Torvalds
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=4d8e3fd30607260857v17bde4afqbe68fde583d2f15f@mail.gmail.com \
--to=paolo.ciarrocchi@gmail.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=git@vger.kernel.org \
--cc=torvalds@osdl.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