[tasks] 01/01: Add 'upstream patches' tasks from meeting #6.

[Daniel Shahaf]

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

danielsh-guest pushed a commit to branch master
in repository tasks.

commit 1adc19995fe4c595fcb0afd4245c06fa7b8de49d
Author: Daniel Shahaf <d.s at daniel.shahaf.name>
Date:   Thu Jan 12 20:09:54 2017 +0000

    Add 'upstream patches' tasks from meeting #6.
---
 pending.txt | 4 ++++
 1 file changed, 4 insertions(+)

diff --git a/pending.txt b/pending.txt
index 5204fa9..e4b6f48 100644
--- a/pending.txt
+++ b/pending.txt
@@ -16,6 +16,10 @@ Pending
 
 - send mail to -devel to discuss mass-NMU of wishlist bugs with patches… and putting reproducibility in debian-policy, as a should. for stretch and sell it as marketing feature. our downstreams are loving it. (h01ger)
 
+- upstream patches:
+  - talk to qa@ about tracking patches without DEP-3 "Forwarded: yes" status
+  - send those patches upstream, or at least to distropatches (https://github.com/distropatches/reproducible-builds)
+
 - forgot to do at summit in Berlin: Discuss adding clamping to s-d-e spec
 
 - .buildinfo file workflow design problem: Autobuilders only generate the arch:all and arch:any binary packages from the source package they are given. They do not regenerate the source package. Thus, they will call dpkg-buildpackage with --build=any or --build=all which in turn will create a .buildinfo that doesn't contain the source hash. (see #774415)

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