From: "jonsmirl@gmail.com" <jonsmirl@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: Recovering from a bad object
Date: Sun, 22 May 2011 18:47:23 -0400 [thread overview]
Message-ID: <BANLkTinbNXRkRdDusz6=-aJkxW==rGVVeg@mail.gmail.com> (raw)
In-Reply-To: <BANLkTinPOYH_pJsFkbQHCb_H5GhyTn+xhg@mail.gmail.com>
On Sun, May 22, 2011 at 6:31 PM, jonsmirl@gmail.com <jonsmirl@gmail.com> wrote:
> Looks like the corrupt object is ok in the object store.
>
> I checked out about 20 of the dangling objects. They all start off with...
>
> commit aa96dc2459563fa362bc53597cb076d93bcc884a
> Author: Jon Smirl <jonsmirl@gmail.com>
> Date: Sat Mar 19 13:30:55 2011 -0400
>
> refresh (create temporary patch) d666137c5fe3ee4c4c812c706b1a3c539405ffd0
>
>
> That's stgit leaving all those dangling references. I will experiment
> with the current stgit and see if it is still leaving the dangling
> references or if they are leftovers from an old bug.
I've confirmed it is a problem in stgit. I made a brand new clone and
did three refreshes in it.
jonsmirl@terra:/home/apps/lpc3131/linux$ git fsck
dangling commit 78fe5e16791996ffa3e60eb8015c8782c02496ca
dangling commit 5d41f5a4368036f18a021a8e72ad5577839070c6
dangling commit b3b2be2f2a78d356059d92dbb937f9df726de166
Now I have three dangling commits.
Now I don't know enough about stgit works. Are those really dangling
commits from stgit abandoning temporary commits, or is stgit tracking
them and 'git fsck' simply doesn't have a reference to them.
>
> --
> Jon Smirl
> jonsmirl@gmail.com
>
--
Jon Smirl
jonsmirl@gmail.com
next prev parent reply other threads:[~2011-05-22 22:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-21 23:03 Recovering from a bad object jonsmirl
2011-05-22 20:42 ` Junio C Hamano
2011-05-22 22:31 ` jonsmirl
2011-05-22 22:47 ` jonsmirl [this message]
2011-05-23 2:09 ` Junio C Hamano
2011-09-18 19:31 ` Enrico Weigelt
2011-09-18 19:48 ` jonsmirl
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='BANLkTinbNXRkRdDusz6=-aJkxW==rGVVeg@mail.gmail.com' \
--to=jonsmirl@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).