Emily Ren schrieb:You can't, and that is so by design. Consider this: You accidentally push a branch with confidential data to a public repository. You notice it early, and quickly delete the branch using 'git push the-repo :refs/heads/that-branch'. At this time the objects with the confidential data are still lingering in the public repository. But with the current behavior noone can access them even if the SHA1 happens to be known. -- Hannes -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
| Greg KH | Og dreams of kernels |
| Jens Axboe | [PATCH 31/33] Fusion: sg chaining support |
| Arnd Bergmann | Re: finding your own dead "CONFIG_" variables |
| Mark Brown | [PATCH 2/2] Subject: natsemi: Allow users to disable workaround for DspCfg reset |
| Tony Breeds | [LGUEST] Look in object dir for .config |
git: | |
| Brian Downing | Re: Git in a Nutshell guide |
| John Benes | Re: master has some toys |
| Matthias Lederhofer |
