Re: [PATCH xorg-docs 1/4] Update docs for gitlab migration

On 11/19/18 07:05 AM, Adam Jackson wrote: On Sat, 2018-11-17 at 14:46 -0800, Alan Coopersmith wrote: in future releases. More details on patch submission and review process are available on the -http://www.x.org/wiki/Development/Documentation/SubmittingPatches;>

Re: [PATCH xorg-docs 1/4] Update docs for gitlab migration

On Sat, 2018-11-17 at 14:46 -0800, Alan Coopersmith wrote: > diff --git a/general/README.xml b/general/README.xml > index 7446fa0..b7fe484 100644 > --- a/general/README.xml > +++ b/general/README.xml > @@ -243,13 +243,12 @@ page. > > > If you have any new work or enhancements/bug fixes for

Re: [PATCH xorg-docs 2/4] Update configure.ac for gitlab migration

On 11/17/18 02:46 PM, Alan Coopersmith wrote: Signed-off-by: Alan Coopersmith --- configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index 80d7307..de17002 100644 --- a/configure.ac +++ b/configure.ac @@ -24,7 +24,7 @@ dnl Process

[PATCH xorg-docs 1/4] Update docs for gitlab migration

Signed-off-by: Alan Coopersmith --- general/README.xml| 15 +++ general/ReleaseNotes.xml | 14 ++ general/platforms/Solaris.xml | 3 +-- man/XOrgFoundation.man| 4 ++-- registry | 2 +- 5 files changed, 17 insertions(+), 21

[PATCH xorg-docs 3/4] Update MAINTAINERS for gitlab migration

Replace dozens of links to wiki.x.org with gitlab project links Change status to "Deactivated" for projects marked "Archived" in gitlab Signed-off-by: Alan Coopersmith --- MAINTAINERS | 218 ++-- 1 file changed, 109 insertions(+), 109

[PATCH xorg-docs 0/4] Update docs for gitlab migration & http->https

This series is also covered by https://gitlab.freedesktop.org/xorg/doc/xorg-docs/merge_requests/1 but email still seems to get more attention than merge requests on the less active repos. [PATCH xorg-docs 1/4] Update docs for gitlab migration [PATCH xorg-docs 2/4] Update configure.ac for gitlab

[PATCH xorg-docs 2/4] Update configure.ac for gitlab migration

Signed-off-by: Alan Coopersmith --- configure.ac | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/configure.ac b/configure.ac index 80d7307..de17002 100644 --- a/configure.ac +++ b/configure.ac @@ -24,7 +24,7 @@ dnl Process this file with autoconf to create configure.

Re: [PATCH app/xcursorgen v3] Update README for gitlab migration

Alan Coopersmith writes: > On 11/13/18 05:13 PM, Ray Strode wrote: >> hi, >> >> On Tue, Nov 13, 2018, 7:57 PM Alan Coopersmith > wrote: >> >> Anyone have a preference?   Shipping README.md seems easier - will it >> cause >> problems for any distros

Re: [PATCH app/xcursorgen v3] Update README for gitlab migration

On 11/13/18 05:13 PM, Ray Strode wrote: hi, On Tue, Nov 13, 2018, 7:57 PM Alan Coopersmith wrote: Anyone have a preference?   Shipping README.md seems easier - will it cause problems for any distros or packagers? i think README.md is the right way

Re: [PATCH app/xcursorgen v3] Update README for gitlab migration

On 11/13/18 08:50 PM, Keith Packard wrote: Alan Coopersmith writes: 3rd choice - this seems to work for me, shipping a file named README in the tarball without any Makefile modifications: Yikes! Scary git-fu! Maybe we can see if cmark-gfm is available? That's the github fork that parses

Re: [PATCH app/xcursorgen v3] Update README for gitlab migration

On Tue, Nov 13, 2018 at 08:50:11PM -0800, Keith Packard wrote: > Alan Coopersmith writes: > > > 3rd choice - this seems to work for me, shipping a file named README in the > > tarball without any Makefile modifications: > > Yikes! Scary git-fu! > > Maybe we can see if cmark-gfm is available?

Re: [PATCH app/xcursorgen v3] Update README for gitlab migration

Alan Coopersmith writes: > 3rd choice - this seems to work for me, shipping a file named README in the > tarball without any Makefile modifications: Yikes! Scary git-fu! Maybe we can see if cmark-gfm is available? That's the github fork that parses more useful common mark syntax files, which

Re: [PATCH app/xcursorgen v3] Update README for gitlab migration

hi, On Tue, Nov 13, 2018, 7:57 PM Alan Coopersmith Anyone have a preference? Shipping README.md seems easier - will it cause > problems for any distros or packagers? > i think README.md is the right way to go. presumably any packaging challenges have been ironed out by now considering how

Re: [PATCH app/xcursorgen v3] Update README for gitlab migration

On 11/13/18 04:57 PM, Alan Coopersmith wrote: On 11/13/18 05:41 AM, Julien Cristau wrote: LGTM.  Thanks Alan! Thanks to you, Peter, & Ray for reviews.   I merged this, and thought "Okay, time to cut a new release."  And then I found the mistake. automake automatically includes a file named

Re: [PATCH app/xcursorgen v3] Update README for gitlab migration

On 11/13/18 05:41 AM, Julien Cristau wrote: LGTM. Thanks Alan! Thanks to you, Peter, & Ray for reviews. I merged this, and thought "Okay, time to cut a new release." And then I found the mistake. automake automatically includes a file named "README" in the tarball. It does not include a

Re: [PATCH app/xcursorgen v3] Update README for gitlab migration

On Mon, Nov 12, 2018 at 11:55:18AM -0800, Alan Coopersmith wrote: > Signed-off-by: Alan Coopersmith Reviewed-by: Peter Hutterer > --- > > v2: Moved to README.md and reduced whitespace in front of URLs so that > gitlab renders them as links instead of code fragements - see >

[PATCH app/xcursorgen v3] Update README for gitlab migration

Signed-off-by: Alan Coopersmith --- v2: Moved to README.md and reduced whitespace in front of URLs so that gitlab renders them as links instead of code fragements - see https://gitlab.freedesktop.org/alanc/xcursorgen for formatted view Restored link to Submitting Patches page so

[PATCH app/xcursorgen v2] Update README for gitlab migration

Signed-off-by: Alan Coopersmith --- v2: Moved to README.md and reduced whitespace in front of URLs so that gitlab renders them as links instead of code fragements - see https://gitlab.freedesktop.org/alanc/xcursorgen for formatted view Restored link to Submitting Patches page so

gitlab migration: xserver issues enabled

I've enabled filing gitlab issues for xserver, as people were trying to file bugs against xorg/meta (which is not the right place). Expect bugzilla migration to start happening later this week and take... well, I don't know how long, I'll be attempting to triage/close old issues as I go and I

Re: [PATCH app/xcursorgen] Update README for gitlab migration

hi, On Mon, Oct 1, 2018, 1:11 PM Alan Coopersmith wrote: > Does anyone have feedback on changing our README's like this? it should probably be renamed README.md so it shows up in the gitlab view better. Ray ___ xorg-devel@lists.x.org: X.Org

Re: [PATCH app/xcursorgen] Update README for gitlab migration

On Mon, Oct 01, 2018 at 10:11:07AM -0700, Alan Coopersmith wrote: > Does anyone have feedback on changing our README's like this? While I > sent this out as a patch to a specific repo, I figured once we have > an agreed upon template, we'd apply it to all of the repos. oh well, if you ask... :)

Re: [PATCH app/xcursorgen] Update README for gitlab migration

Does anyone have feedback on changing our README's like this? While I sent this out as a patch to a specific repo, I figured once we have an agreed upon template, we'd apply it to all of the repos. -alan- On 09/22/18 12:11 PM, Alan Coopersmith wrote: Signed-off-by: Alan Coopersmith

[PATCH app/xcursorgen] Update README for gitlab migration

Signed-off-by: Alan Coopersmith --- README | 12 ++-- 1 file changed, 2 insertions(+), 10 deletions(-) diff --git a/README b/README index 6e46f96..f830ada 100644 --- a/README +++ b/README @@ -1,25 +1,17 @@ xcursorgen prepares X11 cursor sets for use with libXcursor. All questions

Re: gitlab migration

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 (including account update plans, please read)

On Wed, 2018-08-01 at 14:38 +0200, Guillem Jover wrote: > It would be nice if the xorg.modules (from modular) got updated too, so > that some of this could be automated locally. :) My goodness, we have written this down so many slightly different ways. I've pushed some updates that I hope are

Re: gitlab migration (including account update plans, please read)

On Sun, 2018-07-29 at 21:49:44 +0100, Daniel Stone wrote: > On Sun, 29 Jul 2018 at 16:53, Alan Coopersmith > wrote: > > On 07/29/18 03:07 AM, Daniel Stone wrote: > > > This took a little longer than hoped, but all the repos have now been > > > moved. Great! :) > > I updated all my local clones

Re: gitlab migration (including account update plans, please read)

On 07/29/18 01:49 PM, Daniel Stone wrote: Not wrong as such, just moved. These are the modules which (as requested) changed relative path during the migration: xorg/app/bdftopcf -> xorg/util/bdftopcf xorg/app/rendercheck -> xorg/test/rendercheck xorg/app/x11perf -> xorg/test/x11perf

Re: gitlab migration (including account update plans, please read)

Hi Alan, On Sun, 29 Jul 2018 at 16:53, Alan Coopersmith wrote: > On 07/29/18 03:07 AM, Daniel Stone wrote: > > This took a little longer than hoped, but all the repos have now been moved. > > Huge thanks for doing this. > > I updated all my local clones with: > > git remote set-url origin `git

Re: gitlab migration (including account update plans, please read)

On 07/29/18 03:07 AM, Daniel Stone wrote: Hi, On Mon, 23 Jul 2018 at 16:24, Adam Jackson wrote: My earlier assertion about the git url not being changed is only true for pulls. For pushes, you will indeed need to update the remote to the new URL: $ git remote set-url origin

Re: gitlab migration (including account update plans, please read)

Hi, On Mon, 23 Jul 2018 at 16:24, Adam Jackson wrote: > My earlier assertion about the git url not being changed is only true > for pulls. For pushes, you will indeed need to update the remote to the > new URL: > > $ git remote set-url origin ssh://g...@gitlab.freedesktop.org/xorg/xserver > >

More gitlab migration (this time it's personal)

If you want to follow anything I'm working on, follow it here: https://gitlab.freedesktop.org/ajax/xserver/ I'll be using merge requests under that repo to track the progress of my own development branches, and issues to track known defects that someone should work on. I won't be looking at

Re: gitlab migration (including account update plans, please read)

On Mon, 2018-07-23 at 11:23 -0400, Adam Jackson wrote: > Nobody did, so, this is done now. > > My earlier assertion about the git url not being changed is only true > for pulls. For pushes, you will indeed need to update the remote to the > new URL: > > $ git remote set-url origin

Re: gitlab migration (including account update plans, please read)

On Mon, 2018-07-09 at 14:30 -0400, Adam Jackson wrote: > Currently the xorg group in gitlab is derived from the pre-existing > freedesktop LDAP group. This is a bit excessive, there's over 250 > people in the group in total and not even a fifth of those are > regularly active. If you're both a

Re: gitlab migration (including account update plans, please read)

On Mon, 2018-07-02 at 10:23 -0700, Keith Packard wrote: > For the first step, I'd like to propose moving the x server git > repository to gitlab in the coming week, with the switch-over happening > on the morning of July 9. This is now done: https://gitlab.freedesktop.org/xorg/xserver The old

Re: gitlab migration

Adam Jackson writes: > I don't really see a reason not to move the repos for everything. It's > a pretty invisible change since the old URLs keep working, and I'm > itchy to see CI wired up. Sounds good to me; I was trying to not over-load poor Daniel. If he's up for it, or can use help from

Re: gitlab migration

On Mon, 2018-07-02 at 10:23 -0700, Keith Packard wrote: > Adam Jackson writes: > > > I'd like us to start moving repos and bug tracking into gitlab. > > I would also like to get to a merge-request model at some > point. However, I think we can take this in stages and start by moving > the git

Re: gitlab migration

Adam Jackson writes: > I'd like us to start moving repos and bug tracking into gitlab. I would also like to get to a merge-request model at some point. However, I think we can take this in stages and start by moving the git repos over to gitlab, and then move the bugs over, and finally start

Re: gitlab migration

On Fri, 2018-06-08 at 14:08 -0400, 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: > >

Re: gitlab migration

On Tue, 2018-06-12 at 17:38 -0400, James Cloos wrote: > Two comments: > > BZ is superior to GL (or GH or the like). > > Mailing lists are vastly superior to any web-only crap. 'web-only' is only a problem until you actually go write a command line client for it. Which, you can do if you really

Re: gitlab migration

Hi Felix, On Wed, 13 Jun 2018 at 10:24, Felix Miata wrote: > Daniel Stone composed on 2018-06-13 09:24 (UTC+0100): > > Felix Miata wrote: > >> James Cloos composed on 2018-06-12 17:38 (UTC-0400): > >> > BZ is superior to GL (or GH or the like). > > >> Strongly agree, especially for returning

Re: gitlab migration

Hi Felix, On Wed, 13 Jun 2018 at 04:17, Felix Miata wrote: > James Cloos composed on 2018-06-12 17:38 (UTC-0400): > > Two comments: > > > BZ is superior to GL (or GH or the like). > > Strongly agree, especially for returning useful search results!!! What kind of searches have you tried which

Re: gitlab migration

On Tue, 12 Jun 2018 at 22:36, James Cloos wrote: > > "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

Re: gitlab migration

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

Re: gitlab migration

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

Re: gitlab migration

James Cloos composed on 2018-06-12 17:38 (UTC-0400): > Two comments: > BZ is superior to GL (or GH or the like). Strongly agree, especially for returning useful search results!!! > Mailing lists are vastly superior to any web-only Strongly agree!!! -- "Wisdom is supreme; therefore get

Re: gitlab migration

Two comments: BZ is superior to GL (or GH or the like). Mailing lists are vastly superior to any web-only crap. -JimC -- James Cloos OpenPGP: 0x997A9F17ED7DAEA6 ___ xorg-devel@lists.x.org: X.Org development Archives:

Re: gitlab migration

> "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

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

Re: gitlab migration

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

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

Re: gitlab migration

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

Re: gitlab migration

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

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

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

Re: gitlab migration

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

Re: gitlab migration

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: > >

Re: gitlab migration

On 9 June 2018 at 00:11, Eric Anholt wrote: > Adam Jackson writes: >> 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

Re: gitlab migration

Adam Jackson writes: > 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: > >

gitlab migration

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.org/archives/mesa-dev/2018-May/195634.html This