On Saturday 05 February 2011 19:58:55 Thomas Lübking wrote:
> Hi,
> i've "accidentally" pushed a "4.6" (NOT "KDE/4.6") branch to remote
> (sorry),
> where it does oc. not belong...
>
> However "git push origin :4.6" fails by:
>
> remote: D refs/heads/4.6 kde-workspace luebking DENIED by fallthru
On 5 February 2011 20:39, Stefan Majewsky
wrote:
> Don't we have this yet? I'm using exactly this approach for my work
> branches in libtagaro (cf. kde:libtagaro and
> kde:clones/libtagaro/majewsky/work). The only fear I'm having is that
> I'll once run into this 100-commits-per-push-operation lim
On Sat, Feb 5, 2011 at 9:12 PM, John Tapsell wrote:
> The way that it works for the public Qt repository is that no one can
> create or delete branches. But anyone can clone the repository, and
> then create/delete branches there as they want.
>
> Shouldn't we have something similar?
Don't we ha
Am 05.02.2011, 21:03 Uhr, schrieb Ben Cooksley :
Only repository admins are allowed to delete branches on git.kde.org.
I have now deleted this branch.
Ok, thanks alot - and sorry again.
Cheers,
Thomas
On 5 February 2011 20:03, Ben Cooksley wrote:
> On Sun, Feb 6, 2011 at 8:58 AM, Thomas Lübking
> wrote:
>> Hi,
>> i've "accidentally" pushed a "4.6" (NOT "KDE/4.6") branch to remote (sorry),
>> where it does oc. not belong...
>>
>> However "git push origin :4.6" fails by:
>>
>> remote: D refs/hea
On Sun, Feb 6, 2011 at 8:58 AM, Thomas Lübking
wrote:
> Hi,
> i've "accidentally" pushed a "4.6" (NOT "KDE/4.6") branch to remote (sorry),
> where it does oc. not belong...
>
> However "git push origin :4.6" fails by:
>
> remote: D refs/heads/4.6 kde-workspace luebking DENIED by fallthru
> remote:
Hi,
i've "accidentally" pushed a "4.6" (NOT "KDE/4.6") branch to remote
(sorry),
where it does oc. not belong...
However "git push origin :4.6" fails by:
remote: D refs/heads/4.6 kde-workspace luebking DENIED by fallthru
remote: error: hook declined to update refs/heads/4.6
To ssh://g...@git.