Ian Monroe (2009-01-18 10:29 -0600) wrote:
> On Sun, Jan 18, 2009 at 10:15 AM, Robert Wohlrab wrote:
>> Please note that git tracks everything by its sha1. So rebasing a
>> branch will change its sha1's and you will get the same stuff as
>> above. So I would say nobody should have forced push rights access to
>> the official branches. But this is something your guys have to
>> "auskaspern" (sry, don't know an equivalent word in english - just
>> speak with other amarok devs what they think about forced pushs)
>
> Yes no force pushes I think. :) Central repos aren't meant for that
> sort of thing.
Note that there are also options to prevent forced pushes and deletes.
It might be good idea to set these on the public main repository:
receive.denyNonFastForwards
If set to true, git-receive-pack will deny a ref update which is
not a fast forward. Use this to prevent such an update via a
push, even if that push is forced. This configuration variable
is set when initializing a shared repository.
receive.denyDeletes
If set to true, git-receive-pack will deny a ref update that
deletes the ref. Use this to prevent such a ref deletion via a
push.
_______________________________________________
Kde-scm-interest mailing list
Kde-scm-interest@kde.org
https://mail.kde.org/mailman/listinfo/kde-scm-interest
