[Reproducible-commits] [notes] 03/03: comments can be arch-specific or upstream and architectures can be called differently in different projects

Holger Levsen holger at layer-acht.org
Tue Jun 14 23:50:38 UTC 2016


This is an automated email from the git hooks/post-receive script.

holger pushed a commit to branch multi-project-syntax
in repository notes.

commit 938de6939861401e16ea5c6e9bc595e701722c10
Author: Holger Levsen <holger at layer-acht.org>
Date:   Wed Jun 15 01:49:34 2016 +0200

    comments can be arch-specific or upstream and architectures can be called differently in different projects
---
 README | 9 ++++++++-
 1 file changed, 8 insertions(+), 1 deletion(-)

diff --git a/README b/README
index cf75710..b8fa523 100644
--- a/README
+++ b/README
@@ -39,10 +39,15 @@ A full entry looks like the following:
        arch-armhf:
          issues:
            - blacklisted_on_armhf
+         comments: |
+           this is just an silly architecture specific example comment.
      ArchLinux:
        version: 1.7.3.2
        issues:
          - ftbfs_due_to_gcc7_transition
+       arch-x86
+         comments: |
+           another silly comment explaining architectures can be called differently.
      FreeBSD:
        name: gnu-socat
        version: 1.8
@@ -50,7 +55,9 @@ A full entry looks like the following:
        - timestamps_from_cpp_macros
      bugs:
        - https://githost.example.org/issues/4223 
-  
+     comments: |
+       Upstream said they will fix the issue soon.
+ 
 Every field is optional, although a version number would be useful to do
 cleanups.
 

-- 
Alioth's /usr/local/bin/git-commit-notice on /srv/git.debian.org/git/reproducible/notes.git



More information about the Reproducible-commits mailing list