[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
branch master updated: website: guix-data-service-missing-blog-post: Fix
From: |
Ludovic Courtès |
Subject: |
branch master updated: website: guix-data-service-missing-blog-post: Fix typo. |
Date: |
Sun, 08 Nov 2020 17:43:35 -0500 |
This is an automated email from the git hooks/post-receive script.
civodul pushed a commit to branch master
in repository guix-artwork.
The following commit(s) were added to refs/heads/master by this push:
new a035c6f website: guix-data-service-missing-blog-post: Fix typo.
a035c6f is described below
commit a035c6faa24ea0241750d718d62a34d3f1198d1f
Author: Ludovic Courtès <ludo@gnu.org>
AuthorDate: Sun Nov 8 23:43:12 2020 +0100
website: guix-data-service-missing-blog-post: Fix typo.
* website/posts/guix-data-service-missing-blog-post.md (tags): "patches"
-> "packages".
---
website/posts/guix-data-service-missing-blog-post.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/website/posts/guix-data-service-missing-blog-post.md
b/website/posts/guix-data-service-missing-blog-post.md
index 8dceb4c..e59d3fb 100644
--- a/website/posts/guix-data-service-missing-blog-post.md
+++ b/website/posts/guix-data-service-missing-blog-post.md
@@ -22,7 +22,7 @@ blog post covering what it is and why it exists.
The initial motivation came from trying to automate aspects of
reviewing patches for Guix. If you have some patches for Guix, one
aspect of review might be to apply the patches and then build the
-affected patches. How do you know what packages are affected though?
+affected packages. How do you know what packages are affected though?
You could try and guess based on the content of the patches, and this
could work some of the time, but because Guix packages relate to one
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- branch master updated: website: guix-data-service-missing-blog-post: Fix typo.,
Ludovic Courtès <=