Re: Recovering from repository corruption

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Tue, Jun 10, 2008 at 16:14, Jakub Narebski <jnareb@xxxxxxxxx> wrote:
> Please remember that in such clone you _don't_ have grafts info (unless
> you copy it manually), so it is a good test if you correctly rewrote
> history using git-filter-branch.  So take a look at history in your
> clone using gitk or some similar tool.
>
> In the history you mentioned:
>
>    ...---a---*   b---c---d---*   e---...
>           \     /         \     /
>            \-X-/           \---/
>
> you should rewritr from 'a'=='X^' to, and including 'e' (and not only
> from 'd').

So I re-did the filter-branch as:

    git-filter-branch HEAD
28aa69aafc8ae901e588f6d341b3e6d3558c6d26^..163a93df14d246dee91c3a503e6372b8313f337d

Now cloning still works and only shows dangling commits --- no errors!

-- 
                              Denis
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html

[Index of Archives]     [Linux Kernel Development]     [Gcc Help]     [IETF Annouce]     [DCCP]     [Netdev]     [Networking]     [Security]     [V4L]     [Bugtraq]     [Yosemite]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Linux SCSI]     [Fedora Users]

  Powered by Linux