Revert "config: remove date from URLs"

This reverts commit 1ad04df.

_config.yml

@@ -111,9 +111,9 @@ text:
 
 # Build settings
 markdown:     kramdown
-permalink:    /:title.html
 redcarpet:
   extensions: ['smart', 'tables', 'with_toc_data']
+permalink:    pretty
 paginate:     10
 sass:
   style: compressed

_posts/2024-01-01-kernel-contributor-1.md

@@ -88,4 +88,4 @@ A simple `git grep TODO` will show you that there are literally hundreds of pend
 
 ## I found my way, what's next?
 
-You are not far from becoming a kernel contributor, so just work on your patches until you think they are ready. If you want to avoid some typical and often silly mistakes, [the second episode](/kernel-contributor-2) will save you some time. Then you will start the submission process to get your changes accepted upstream. Ok, but how do I trigger that process and how does it work? Be patient, that is exactly the topic of the [third and last episode](/kernel-contributor-3) :wink:
+You are not far from becoming a kernel contributor, so just work on your patches until you think they are ready. If you want to avoid some typical and often silly mistakes, [the second episode](/2024/01/03/kernel-contributor-2) will save you some time. Then you will start the submission process to get your changes accepted upstream. Ok, but how do I trigger that process and how does it work? Be patient, that is exactly the topic of the [third and last episode](/2024/01/05/kernel-contributor-3) :wink:

_posts/2024-01-03-kernel-contributor-2.md

@@ -6,7 +6,7 @@ summary:    Things to consider while making changes
 tags:       contributor foss kernel linux
 ---
 
-This is the second episode of my series on how to become a Linux kernel contributor, where I will show you some typical mistakes you should avoid while working on your first contributions. If you are looking for ideas to make your first contribution to the kernel, please take a look at the [first episode](/kernel-contributor-1). If you just want to send your changes upstream, go for the [third episode](/kernel-contributor-3)... but read this one fast just in case.
+This is the second episode of my series on how to become a Linux kernel contributor, where I will show you some typical mistakes you should avoid while working on your first contributions. If you are looking for ideas to make your first contribution to the kernel, please take a look at the [first episode](/2024/01/01/kernel-contributor-1). If you just want to send your changes upstream, go for the [third episode](/2024/01/05/kernel-contributor-3)... but read this one fast just in case.
 
 ## Make sure no one is doing the same
 
@@ -101,4 +101,4 @@ Simply save the script as *post-commit* in the *.git/hooks/* directory.
 
 ## My code is flawless, how do I send it upstream?
 
-Even flawless code can require modifications and extensions, but you will learn that during the process that you are about to trigger. The [last episode](/kernel-contributor-3) of the series will walk you through the steps you will have to follow. Stay tuned and share knowledge!
+Even flawless code can require modifications and extensions, but you will learn that during the process that you are about to trigger. The [last episode](/2024/01/05/kernel-contributor-3) of the series will walk you through the steps you will have to follow. Stay tuned and share knowledge!

_posts/2024-01-05-kernel-contributor-3.md

@@ -8,7 +8,7 @@ tags:       contributor foss kernel linux
 
 This is the third and last episode of my series about how to become a Linux kernel contributor. It is a bit longer than the others because it shows step by step the whole submission process. Nowadays few people can still read or pay attanetion for 15 minutes straight, but try your best. Otherwise, be ready to spend hours fixing what you ignored here :wink:
 
-If you are looking for ideas to make your first contribution to the kernel, please take a look at the [first episode](/kernel-contributor-1). If you want to avoid beginner mistakes in your first contribution, the [second episode](/kernel-contributor-2) may be helpful. If you read the two first episodes, or you think you don't need them (<span style="color:darkorange"><b>you will miserably fail!</b></span>), welcome to the last episode.
+If you are looking for ideas to make your first contribution to the kernel, please take a look at the [first episode](/2024/01/01/kernel-contributor-1). If you want to avoid beginner mistakes in your first contribution, the [second episode](/2024/01/03/kernel-contributor-2) may be helpful. If you read the two first episodes, or you think you don't need them (<span style="color:darkorange"><b>you will miserably fail!</b></span>), welcome to the last episode.
 
 Getting your changes accepted upstream might be a complex and frustrating process if you don't know how it works. If you are expecting a simple PR on GitHub, this article was made for you.
 

_posts/2024-01-06-b4-for-kernel-contributors.md

@@ -65,7 +65,7 @@ Signed-off-by: Javier Carrasco <[email protected]>
 
 I don't need to explain the content, because b4 does it pretty well. It even added a *Signed-off-by* to the cover letter. Is b4 not beginner-friendly? It will even refuse to send the series if you don't edit the cover letter :smiley:
 
-Now let's introduce some changes. If you followed the example from the [third episode](/kernel-contributor-3) about how to become a Linux kernel contributor, this will look familiar:
+Now let's introduce some changes. If you followed the example from the [third episode](/2024/01/06/kernel-contributor-3) about how to become a Linux kernel contributor, this will look familiar:
 
 ![dummy-series](/images/posts/2024-01-06-b4-for-kernel-contributors/dummy-series.jpg)