opdavies/oliverdavies.uk
1
0
Fork 0
Code Issues 1 Pull requests Projects 1 Releases Packages Wiki Activity Actions

tome export

Browse source
This commit is contained in:
Oliver Davies 2025-05-30 02:14:32 +01:00
parent 52278c3a53
commit 7a52afab5f
960 changed files with 3670 additions and 2229 deletions
Download patch file Download diff file Expand all files Collapse all files

6
content/node.c99cc7ef-20b0-4743-9638-61cb4beeb5ec.json
View file

@ -82,15 +82,15 @@
],
"body": [
{
"value": "\n <p>The other day, <a href=\"/daily\/2024\/05\/21\/which-commit-has-the-largest-message\">I posted about a script I'd written<\/a> that found the longest commit message in a repository.<\/p>\n\n<p>As I couldn't find a native way to do this with Git, the script loops over each commit in the repository, calculates its length and stores the length and commit SHA in a file.<\/p>\n\n<p>The lines in the file are sorted so the longest commit is first.<\/p>\n\n<p>Whilst I commonly use short parameters, such as <code>git add -p<\/code> when typing commands, in scripts, I prefer to use the equivalent longer parameters, where possible.<\/p>\n\n<p>For example, in the script, I execute this command to sort the lines:<\/p>\n\n<pre><code class=\"bash\">sort \"${result_file}\" --reverse --numeric-sort --output \"${result_file}\"\n<\/code><\/pre>\n\n<p>This could be re-written as:<\/p>\n\n<pre><code class=\"bash\">sort \"${result_file}\" -rn -o \"${result_file}\"\n<\/code><\/pre>\n\n<p>Whilst the original is more verbose and longer to type, I prefer its verbosity which makes it easier for me or others to read and understand in the future.<\/p>\n\n ",
"value": "\n <p>The other day, <a href=\"\/daily\/2024\/05\/21\/which-commit-has-the-largest-message\">I posted about a script I'd written<\/a> that found the longest commit message in a repository.<\/p>\n\n<p>As I couldn't find a native way to do this with Git, the script loops over each commit in the repository, calculates its length and stores the length and commit SHA in a file.<\/p>\n\n<p>The lines in the file are sorted so the longest commit is first.<\/p>\n\n<p>Whilst I commonly use short parameters, such as <code>git add -p<\/code> when typing commands, in scripts, I prefer to use the equivalent longer parameters, where possible.<\/p>\n\n<p>For example, in the script, I execute this command to sort the lines:<\/p>\n\n<pre><code class=\"bash\">sort \"${result_file}\" --reverse --numeric-sort --output \"${result_file}\"\n<\/code><\/pre>\n\n<p>This could be re-written as:<\/p>\n\n<pre><code class=\"bash\">sort \"${result_file}\" -rn -o \"${result_file}\"\n<\/code><\/pre>\n\n<p>Whilst the original is more verbose and longer to type, I prefer its verbosity which makes it easier for me or others to read and understand in the future.<\/p>\n\n ",
"format": "full_html",
"processed": "\n <p>The other day, <a href=\"/daily\/2024\/05\/21\/which-commit-has-the-largest-message\">I posted about a script I'd written<\/a> that found the longest commit message in a repository.<\/p>\n\n<p>As I couldn't find a native way to do this with Git, the script loops over each commit in the repository, calculates its length and stores the length and commit SHA in a file.<\/p>\n\n<p>The lines in the file are sorted so the longest commit is first.<\/p>\n\n<p>Whilst I commonly use short parameters, such as <code>git add -p<\/code> when typing commands, in scripts, I prefer to use the equivalent longer parameters, where possible.<\/p>\n\n<p>For example, in the script, I execute this command to sort the lines:<\/p>\n\n<pre><code class=\"bash\">sort \"${result_file}\" --reverse --numeric-sort --output \"${result_file}\"\n<\/code><\/pre>\n\n<p>This could be re-written as:<\/p>\n\n<pre><code class=\"bash\">sort \"${result_file}\" -rn -o \"${result_file}\"\n<\/code><\/pre>\n\n<p>Whilst the original is more verbose and longer to type, I prefer its verbosity which makes it easier for me or others to read and understand in the future.<\/p>\n\n ",
"processed": "\n <p>The other day, <a href=\"http:\/\/default\/daily\/2024\/05\/21\/which-commit-has-the-largest-message\">I posted about a script I'd written<\/a> that found the longest commit message in a repository.<\/p>\n\n<p>As I couldn't find a native way to do this with Git, the script loops over each commit in the repository, calculates its length and stores the length and commit SHA in a file.<\/p>\n\n<p>The lines in the file are sorted so the longest commit is first.<\/p>\n\n<p>Whilst I commonly use short parameters, such as <code>git add -p<\/code> when typing commands, in scripts, I prefer to use the equivalent longer parameters, where possible.<\/p>\n\n<p>For example, in the script, I execute this command to sort the lines:<\/p>\n\n<pre><code class=\"bash\">sort \"${result_file}\" --reverse --numeric-sort --output \"${result_file}\"\n<\/code><\/pre>\n\n<p>This could be re-written as:<\/p>\n\n<pre><code class=\"bash\">sort \"${result_file}\" -rn -o \"${result_file}\"\n<\/code><\/pre>\n\n<p>Whilst the original is more verbose and longer to type, I prefer its verbosity which makes it easier for me or others to read and understand in the future.<\/p>\n\n ",
"summary": null
}
],
"feeds_item": [
{
"imported": "1970-01-01T00:33:45+00:00",
"imported": "1970-01-01T00:32:50+00:00",
"guid": null,
"hash": "345a3eeaf689f5cb4490ec578563ae9f",
"target_type": "feeds_feed",