This is an automated email from the git hooks/post-receive script.
praiskup pushed a commit to annotated tag example-1.0.12-1
in repository copr/copr.
commit 83c06acac3a094de4fa3c066ae0c0f319ff4409e
Author: Michal Novotný <clime7(a)gmail.com>
AuthorDate: Tue Oct 31 22:06:10 2017 +0100
Update README.md
---
README.md | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/README.md b/README.md
index fa54beb..8acd12f 100644
--- a/README.md
+++ b/README.md
@@ -21,7 +21,7 @@ If you use `rpm/your.spec`, then the `subpkg1/my.spec` is just a normal
file and
contains a spec file or not if you additionaly say what spec file should be used for SRPM
generation.
Knowing that **subpackage** is really formed by any `spec file` together with some
`source directory` makes formal defintions of **flat** and **layered** more complicated.
Let's just say that
[
blog-tutorial-flat-unpacked](https://github.com/clime/blog-tutorial-flat-...
repository is called **flat** because `source directory` for its only subpackage is a root
directory and this repository is **layered** because it contains at least one subpackage
of which its `source directory` is n [...]
-Note that there can be no subpackage in a repository if that repository does not contain
a spec file.
+Note that there can be no subpackages in a repository if that repository does not contain
a spec file.
What is probably even more curious is the true difference between **packed** and
**unpacked** subpackages. Previously, we have said that:
--
To stop receiving notification emails like this one, please contact
the administrator of this repository.