Rebase of kopete branch and push it to master

Pali Rohár pali.rohar at gmail.com
Tue Jan 16 22:20:30 UTC 2018


On Tuesday 16 January 2018 23:05:42 Albert Astals Cid wrote:
> El dimarts, 16 de gener de 2018, a les 0:45:27 CET, Pali Rohár va escriure:
> > On Tuesday 16 January 2018 00:32:44 Albert Astals Cid wrote:
> > > El dimarts, 16 de gener de 2018, a les 0:09:50 CET, Pali Rohár va 
> escriure:
> > > > On Tuesday 16 January 2018 00:06:29 Albert Astals Cid wrote:
> > > > > So is the problem:
> > > > >  a) that you could not push that master-kf5 to master
> > > > 
> > > > Problem is really a).
> > > 
> > > Why is that? You said master-kf5 is just a rebase of kf5 on top of master,
> > > what's the problem of pushing that branch?
> > 
> > Because it does not work.
> > 
> > remote: Push declined - excessive notifications would be sent
> > remote: Please file a KDE Sysadmin bug to continue
> > 
> > Therefore I opened sysadmin ticket T7642 and I was told that I should
> > discuss about it on kde-core-devel.
> 
> Please someone correct me, but that has nothing to do with rebasing no?

Let me explain it again. Under "rebase" I mean result of operation
git rebase. Under "push" I mean result of operation git push.

I took branch kf5 from main kopete repository. Then I rebased it on top
of master and pushed to my personal cloned git repository into branch
master-kf5.

Now I wanted to push this master-kf5 into branch master to main kopete
repository. And push failed.

Strictly speaking it git rebase --onto & git push. But with fact that it
does not use any force push (therefore no history overwrite).

> It's just about a big merge potentially triggering lots of emails and stuff, 
> no?

There is no merge commit, in fact it is just fast forward. And yes it is
a big.

It is a more clear now?

-- 
Pali Rohár
pali.rohar at gmail.com


More information about the kopete-devel mailing list