Re: [PATCH xf86-video-ati] Update README for gitlab migration

2018-11-19 Thread Michel Dänzer
On 2018-11-18 9:22 p.m., Alan Coopersmith wrote: > Signed-off-by: Alan Coopersmith > --- > > Unlike the similar updates to the other Xorg project README's, this leaves > your bugzilla link in place, as well as the instructions to submit patches > to your mailing list instead of suggesting gitlab

[PATCH xf86-video-ati] Update README for gitlab migration

2018-11-18 Thread Alan Coopersmith
Signed-off-by: Alan Coopersmith --- Unlike the similar updates to the other Xorg project README's, this leaves your bugzilla link in place, as well as the instructions to submit patches to your mailing list instead of suggesting gitlab merge requests. Makefile.am | 2 +- README | 25 -

Re: gitlab migration

2018-08-20 Thread Adam Jackson
On Mon, 2018-06-11 at 12:33 +0200, Michel Dänzer wrote: > As the maintainer of xf86-video-amdgpu and -ati, I'm fine with migrating > these to GitLab for Git and patch review. > > However, I'm not sure what to do about bugs/issues. My first thought was > to allow creating new issues in GitLab and

Re: gitlab migration

2018-06-12 Thread James Cloos
> "DS" == Daniel Stone writes: DS> No need to test; it's guaranteed to fail since we require Recaptcha DS> for login due to massive spam issues. Which is of course grossly unethical and malicious and should never be used by any site, under any circumstances. If some sort of captcha is ever

Re: gitlab migration

2018-06-12 Thread Alexander E. Patrakov
Daniel Stone : > > Hi Sylvain, > > On 12 June 2018 at 13:38, wrote: > > On Tue, Jun 12, 2018 at 12:34:31PM +0100, Daniel Stone wrote: > >> GitLab has a pretty comprehensive and well-documented API which might > >> help if you don't want to use a web browser. There are also clients > >> like 'lab'

Re: gitlab migration

2018-06-12 Thread Alexander E. Patrakov
Daniel Stone : > > Hi Alexander, > > On 12 June 2018 at 14:53, Alexander E. Patrakov wrote: > > Daniel Stone : > >> > That said, I could not even create an account with a noscript/xhtml basic > >> > browser (if you want to test that, install the famous noscript module > >> > with an > >> > empty

Re: gitlab migration

2018-06-12 Thread Michel Dänzer
On 2018-06-12 01:35 PM, Daniel Stone wrote: > On 11 June 2018 at 11:33, Michel Dänzer wrote: >> On 2018-06-08 08:08 PM, Adam Jackson wrote: >>> I'd like us to start moving repos and bug tracking into gitlab. >>> Hopefully everyone's aware that gitlab exists and why fdo projects are >>> migrating t

Re: gitlab migration

2018-06-12 Thread Daniel Stone
Hi Alexander, On 12 June 2018 at 14:53, Alexander E. Patrakov wrote: > Daniel Stone : >> > That said, I could not even create an account with a noscript/xhtml basic >> > browser (if you want to test that, install the famous noscript module with >> > an >> > empty "white list" in firefox or chrom

Re: gitlab migration

2018-06-12 Thread sylvain . bertrand
On Tue, Jun 12, 2018 at 01:41:55PM +0100, Daniel Stone wrote: > Hi Sylvain, > > On 12 June 2018 at 13:38, wrote: > > On Tue, Jun 12, 2018 at 12:34:31PM +0100, Daniel Stone wrote: > >> GitLab has a pretty comprehensive and well-documented API which might > >> help if you don't want to use a web b

Re: gitlab migration

2018-06-12 Thread Daniel Stone
Hi Sylvain, On 12 June 2018 at 13:38, wrote: > On Tue, Jun 12, 2018 at 12:34:31PM +0100, Daniel Stone wrote: >> GitLab has a pretty comprehensive and well-documented API which might >> help if you don't want to use a web browser. There are also clients >> like 'lab': https://gitlab.com/zaquestio

Re: gitlab migration

2018-06-12 Thread sylvain . bertrand
On Tue, Jun 12, 2018 at 12:34:31PM +0100, Daniel Stone wrote: > Hi Sylvain, > It looks like Mutt is mangling email addresses - I've fixed Michel's. > > On 11 June 2018 at 14:30, wrote: > > On Mon, Jun 11, 2018 at 12:33:52PM +0200, Michel Dänzer wrote: > >> Adding the amd-gfx list, in cases someb

Re: gitlab migration

2018-06-12 Thread Daniel Stone
Hi Michel, On 11 June 2018 at 11:33, Michel Dänzer wrote: > On 2018-06-08 08:08 PM, Adam Jackson wrote: >> I'd like us to start moving repos and bug tracking into gitlab. >> Hopefully everyone's aware that gitlab exists and why fdo projects are >> migrating to it. If not, the thread about Mesa's

Re: gitlab migration

2018-06-12 Thread Daniel Stone
Hi Sylvain, It looks like Mutt is mangling email addresses - I've fixed Michel's. On 11 June 2018 at 14:30, wrote: > On Mon, Jun 11, 2018 at 12:33:52PM +0200, Michel Dänzer wrote: >> Adding the amd-gfx list, in cases somebody there has concerns or other >> feedback. > > For feedback: > I attempt

Re: gitlab migration

2018-06-11 Thread sylvain . bertrand
On Mon, Jun 11, 2018 at 12:33:52PM +0200, Michel Dänzer wrote: > Adding the amd-gfx list, in cases somebody there has concerns or other > feedback. For feedback: I attempted a migration on gitlab of my repos but I was blocked because it's not noscript/xhtml basic browser friendly. I was successfu

Re: gitlab migration

2018-06-11 Thread Michel Dänzer
On 2018-06-08 08:08 PM, Adam Jackson wrote: > I'd like us to start moving repos and bug tracking into gitlab. > Hopefully everyone's aware that gitlab exists and why fdo projects are > migrating to it. If not, the thread about Mesa's migration provides > some useful background: > > https://lists.x