Get Hot New Stuff Dead or Alive?

2019-10-13 Thread Allen Winter
or maybe renamed? How do I find out if there are any GHNS for KOrganizer. The Import->GHNS menu in KOrganizer starts and I see the import dialog ok. but that dialog is empty. I need to know if something is broken with the KOrganizer implementation or if I should remove that feature. Or maybe jus

Re: Get Hot New Stuff Dead or Alive?

2019-10-13 Thread Ben Cooksley
On Mon, Oct 14, 2019 at 6:06 AM Allen Winter wrote: > > or maybe renamed? Hi Allen, > > How do I find out if there are any GHNS for KOrganizer. > The Import->GHNS menu in KOrganizer starts and I see the import dialog ok. > but that dialog is empty. > > I need to know if something is broken with

Can we agree to change gitlab default behaviour from merge to fast-forward merge for all repos?

2019-10-13 Thread Albert Astals Cid
I find the merge behavior to be not what we've been doing in phabricator so given the idea is to maintain our workflows i'd appreciate if we can agree on continue doing the same. https://docs.gitlab.com/ee/user/project/merge_requests/fast_forward_merge.html Opinions? Cheers, Albert

Re: Can we agree to change gitlab default behaviour from merge to fast-forward merge for all repos?

2019-10-13 Thread Nicolas Fella
+1 On Sun, 13 Oct 2019, 22:58 Albert Astals Cid, wrote: > I find the merge behavior to be not what we've been doing in phabricator > so given the idea is to maintain our workflows i'd appreciate if we can > agree on continue doing the same. > > > https://docs.gitlab.com/ee/user/project/merge_req

Re: Can we agree to change gitlab default behaviour from merge to fast-forward merge for all repos?

2019-10-13 Thread Carl Schwan
+ 1 Commit with the name "Merge branch 'branch-name' into 'master' are not helpful. Cheers, Carl On Sunday, October 13, 2019 10:57:20 PM CEST Albert Astals Cid wrote: > I find the merge behavior to be not what we've been doing in phabricator so > given the idea is to maintain our workflows i'd a

Re:Can we agree to change gitlab default behaviour from merge to fast-forward merge for all repos?

2019-10-13 Thread Nate Graham
+1 Nate On Sun, 13 Oct 2019 14:57:20 -0600 aa...@kde.org wrote I find the merge behavior to be not what we've been doing in phabricator so given the idea is to maintain our workflows i'd appreciate if we can agree on continue doing the same. https://docs.gitlab.com/ee/user/proj

Re: Can we agree to change gitlab default behaviour from merge to fast-forward merge for all repos?

2019-10-13 Thread Aleix Pol
On Sun, Oct 13, 2019 at 10:57 PM Albert Astals Cid wrote: > > I find the merge behavior to be not what we've been doing in phabricator so > given the idea is to maintain our workflows i'd appreciate if we can agree on > continue doing the same. > > https://docs.gitlab.com/ee/user/project/merge_r

Re: Can we agree to change gitlab default behaviour from merge to fast-forward merge for all repos?

2019-10-13 Thread Konstantin Kharlamov
On Пн, окт 14, 2019 at 02:42, Aleix Pol wrote: On Sun, Oct 13, 2019 at 10:57 PM Albert Astals Cid wrote: I find the merge behavior to be not what we've been doing in phabricator so given the idea is to maintain our workflows i'd appreciate if we can agree on continue doing the same.