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

2018-11-16 Thread Keith Packard
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

2018-11-16 Thread Alan Coopersmith
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

2018-11-13 Thread Alan Coopersmith
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

2018-11-13 Thread Matthieu Herrb
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

2018-11-13 Thread Keith Packard
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

2018-11-13 Thread Ray Strode
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

2018-11-13 Thread Alan Coopersmith
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

2018-11-13 Thread Alan Coopersmith
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

2018-11-12 Thread Peter Hutterer
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

2018-11-12 Thread Alan Coopersmith
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