Most likely a caching issue, yes. However, I would like to point out that
there's really no reason at all to delete and re-fork like this. The fork
is still part of the same network in either case.
Tekkub
Github General Support
http://support.github.com/
Join us on IRC: #github on freenode.net
Discussion group: [email protected]
On Sat, Jan 24, 2009 at 5:56 PM, runeb <[email protected]> wrote:
>
> I had a fork of rtomayko/rack-contrib, and I had made some commits to
> my fork. I saw that the project had moved to rack/rack-contrib, so I
> deleted my rtomayko fork and forked from rack after my first fork had
> disappeared from my projects list. When I now go to the project page
> for my fork of rack-contrib, it displays my last commit message to my
> previous fork, even though that commit doesnt exist in the fork I
> currently have. Clicking the commit yields a commit-page without any
> files or comments (the previous fork had 1 new file and 1 comment).
> Commit history is also from the previous fork, with some commit-links
> working (empty) and some not found.
>
> Project page with ghost commit:
> http://github.com/runeb/rack-contrib/tree/master
>
> Ghost commit:
>
> http://github.com/runeb/rack-contrib/commit/962cf84b302962c1d6252ea07203c906dbd50559
>
> Ghost commit history:
> http://github.com/runeb/rack-contrib/commits/
>
> Caching problem?
>
> >
>
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"GitHub" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/github?hl=en
-~----------~----~----~----~------~----~------~--~---
