[Kde-scm-interest] pushing rebased shared branches

Ben Cooksley bcooksley at kde.org
Mon Aug 8 20:11:19 UTC 2011

On Tue, Aug 9, 2011 at 3:36 AM, Marcel Wiesweg <marcel.wiesweg at gmx.de> wrote:
>> This solution doesn't address the problems Ben mentioned. 100 commits
>> is a lot though so maybe isn't relevant to the OP.
>> I don't think it matters much whether you rename or delete, especially
>> given that "deleting" a branch is really just renaming it (it gets put
>> in some slightly hidden ref).
> I will have 5 or 6 commits, so no big problem. In the end, it seems the detour
> of rename and or delete will solve the problem and give identical results.
> Just wondering if unreachable blobs are purged from git.kde repositories
> regularly with git gc?

KDE Git repositories create a special ref called a "backup ref" when
destructive actions, such as ref deletions or force-pushes occur. This
means that everything is forever reachable. Normal git clones do not
download these backup refs however.

It is impossible to destroy any data pushed to KDE Git repositories.

> Thanks
> Marcel
> _______________________________________________
> Kde-scm-interest mailing list
> Kde-scm-interest at kde.org
> https://mail.kde.org/mailman/listinfo/kde-scm-interest

Ben Cooksley
KDE Sysadmin

More information about the Kde-scm-interest mailing list