1 |
-----BEGIN PGP SIGNED MESSAGE----- |
2 |
Hash: SHA512 |
3 |
|
4 |
On 17/06/16 15:58, Rich Freeman wrote: |
5 |
> That could actually be generalized. I could see many types of |
6 |
> bugs where the issue is with upstream, and we might want to track |
7 |
> the progress as upstream implements a fix, releases it, and then it |
8 |
> is stabilized on Gentoo. So, maybe we need another state to track |
9 |
> in upstream's VCS vs the Gentoo repo. |
10 |
> |
11 |
> Another approach would be to distinguish between portage as a |
12 |
> Gentoo-hosted upstream, and portage as a package in the Gentoo |
13 |
> repo. The same could apply to any Gentoo-hosted project. |
14 |
I would be fine with either, but honestly this whole thing seems like |
15 |
bikeshedding for the sake of bikeshedding. It's working fine as-is, |
16 |
and I don't recall any complaints that we've been doing it differently |
17 |
to the tree. |
18 |
- -- |
19 |
Alexander |
20 |
bernalex@g.o |
21 |
https://secure.plaimi.net/~alexander |
22 |
-----BEGIN PGP SIGNATURE----- |
23 |
Version: GnuPG v2 |
24 |
|
25 |
iQIcBAEBCgAGBQJXZAJ5AAoJENQqWdRUGk8BXdsQAIvWgBxy/43BFRfVYk5Ah6ke |
26 |
u0yosJvHJe+PWTPQj6YQNJDgmLwohNeyyrDkV4y6PCrObZWkiJgT34LATmJLThCY |
27 |
C+/ZGuxxSjhYJkO3dU51rc6KCXdQ+Uw7Mvc/jxXzB27nuSA1nfKsw2MRfH6Snhdz |
28 |
hGNYiXe8xry+G1t6BBC2BENrZyRdn/KL6T+0bmc0it6iCvfEWjjKSMmS1GUTPK6G |
29 |
6cD7IOmWVJTl1o9fjM0Em78UlqU8LsyeZLSq+W63crRVhhv1ZzbXHWMG+jRq64dO |
30 |
jmI/qnScC0EnhMg2GYxaiHlo/CRcfFQxvSdqCZC5Ll7bnE0ygYaeA1huhXKg2Qgq |
31 |
ibwN8+1s7j/O50lOqFcVYb6GFvUrObA0Db/k1YcVNENsgr5krBQLRrWOiq5pBJ1g |
32 |
ubFP1G6G5xT1wHmf9j3Cd4DKv2IdVP6u//x+TMhP4utcCbszNyH5tQ6mlPE6Z7i0 |
33 |
YRHXODCiRrdHDr6+TZRTq1/nH0wnhSi7yrlU8lbyMsTAXRsWEDPvc4Y+rvVk70Xn |
34 |
OzGHJcMJzCleNcPd3j+9Oqcb2m/hJY0I+70/OnQwcVVUnEzqyM6FAsca0PlIPA8T |
35 |
lEBZyMYtxewB2znMY4cbiLalVVeDBOYvQcS37ygjdxfChJTnZfMgPMM9ffGcXxZ9 |
36 |
7p2rOSvWrDR9i4RqCY6d |
37 |
=vcMe |
38 |
-----END PGP SIGNATURE----- |