blog amdgpu

[jcfrosty]

New AMDGPU blog.

[Enlik]

(continuing from issue #54)
Title suggests 26.06, file name 24.06. Minor stuff but can be annoying when someone gets misguided by this whilst doing something with the repository.

[jcfrosty]

Good point on the naming and the display code conversion. I've fixed the article to say DAL/HAL conversion. Also updated the name to remove confusion with releases.

[Ryuno-Ki]

I still would like to have seen more subheadings, but you already tool over our suggestions and Enlik approved it, so...

Thanks for your contribution!

@Enlik will you take care for publication?

[Enlik]

I used it to mark "I think it's OK" for no better button or icon (I could have used a comment though).

I don't know how to publish the article; I thought you would do it. :)

[jcfrosty]

This would be a great learning opportunity. Since mudler invited me to the group that can commit changes and stuff. Mind teaching us the process?

…

On Wed, Jun 28, 2017, 1:31 PM Enlik ***@***.***> wrote: I used it to mark "I think it's OK" for no better button or icon (I could have used a comment though). I don't know how to publish the article; I thought you would do it. :) — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#55 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANERGWJdByDvakE-q65wLJmoDkiHWdn7ks5sIpwEgaJpZM4OFoJC> .

[Ryuno-Ki]

Ah, it's already live.

After digging through my IRC logs (thanks, @optiz0r!) I found out how we did it.
This may be worth documenting in our README.md.

When accepting a Pull Request, Circle CI kicks in. It merges the changes into gh-pages, so they show up on Sabayon's GitHub Page and are synched to the live instance quickly afterwards.

[optiz0r]

Bullet points in "So when can we expect to see support" paragraph haven't rendered properly. Otherwise LGTM.

[jcfrosty]

I've gone ahead and fixed the bullet points. Seems it needed a line between the paragraph and the bullet lines.

[Enlik]

Ah, it's already live.

It's actually only on the "next.sabayon.org" (I'm not sure if you meant that).

[Enlik]

Ugh, not sure how others thing but I'd prefer this PR (that consists of several small commits) be either merged or squashed.
Not a big issue anyway.

[jcfrosty]

So how does it go live to the main site?

…

On Thu, Jun 29, 2017, 2:13 PM Enlik ***@***.***> wrote: Ugh, not sure how others thing but I'd prefer this PR (that consists of several small commits) be either merged or squashed. Not a big issue anyway. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#55 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ANERGT28q5CD2x9eN0jTWoibVHZVN3esks5sI_dggaJpZM4OFoJC> .

[Ryuno-Ki]

@Enlik Lately I work mostly with rebases, but can pick another strategy next time.

@jcfrosty Circle CI takes care of that.

[Enlik]

FYI, it looks like it has to be merged manually to the production repository. @jcfrosty opened a PR there.

[Ryuno-Ki]

Ah, yes. How could I forget Sabayon/woohoo?!