| 1 |
-----BEGIN PGP SIGNED MESSAGE----- |
| 2 |
Hash: SHA512 |
| 3 |
|
| 4 |
On 05/21/2012 04:00 PM, Rich Freeman wrote: |
| 5 |
> On Mon, May 21, 2012 at 7:58 AM, Ultrabug <ultrabug@g.o> |
| 6 |
> wrote: |
| 7 |
>> It also may be interesting to use the github workflow with |
| 8 |
>> proxy-maintainers (which might also make the proxy-maintainers |
| 9 |
>> project even more visible) ? |
| 10 |
>> |
| 11 |
> |
| 12 |
> Tend to agree, although a big liability will be the fact that |
| 13 |
> we're still not on git ourselves. So, to be useful that github |
| 14 |
> tree would to get regular cvs updates incorporated, and then any |
| 15 |
> content would need to be manually moved over. The trees would be |
| 16 |
> constantly slightly out of sync - what happens if somebody commits |
| 17 |
> a fix without a revbump to git and then the cvs tree refreshes git |
| 18 |
> not showing the change, and so on? |
| 19 |
> |
| 20 |
> I guess for proxy-maintained packages we could just consider the |
| 21 |
> git-tree "official" and do all forward work there without |
| 22 |
> publishing cvs changes automatically. Then cvs updates are just |
| 23 |
> manual copies when things are good in the git tree. However, the |
| 24 |
> second somebody comes along with some library package move or other |
| 25 |
> tree-wide change they're going to make things out of sync unless |
| 26 |
> they know to go update git. |
| 27 |
> |
| 28 |
> Seems like overlays are the best candidate for a place to start |
| 29 |
> since they largely use git already. Maybe this is just one more |
| 30 |
> reason to get the main tree onto git as well... |
| 31 |
> |
| 32 |
> Rich |
| 33 |
> |
| 34 |
It will be a pain from our (proxy-maint) side to use git workflow on a |
| 35 |
cvs tree. Speaking of myself I am not interested in supporting this |
| 36 |
"mixed" kind of collaboration and frankly I see no viable way for |
| 37 |
someone to do that in the long term. |
| 38 |
|
| 39 |
- -- |
| 40 |
Regards, |
| 41 |
Markos Chandras / Gentoo Linux Developer / Key ID: B4AFF2C2 |
| 42 |
-----BEGIN PGP SIGNATURE----- |
| 43 |
Version: GnuPG v2.0.19 (GNU/Linux) |
| 44 |
|
| 45 |
iQIcBAEBCgAGBQJPunj5AAoJEPqDWhW0r/LCN4cP/ipXJI7V0Tpoirtl66gEEPun |
| 46 |
RMjTrkNqsOPjyliQX/AfjSVpDlXCFwImciakVngfy6CQ1A2635VJHcjhSRSfnsKX |
| 47 |
BsBmD19ZIRXpLI7KZYzn9JkRMYQaiEwVTQUdtNpFrQ5r62lrbkJOBypXJZGdA9/a |
| 48 |
l/aw6dTCjb2yXhV6ToRtHXTB396eY6rJuCb/RpDNz557jQ/BOV1HrhDFhhtUZD9h |
| 49 |
GDOdrGmK0dWYoKVU8LN++k6/AU1MTx9YQ9nXXz0m4YbH021Z4BazcPUuCjN3Y4ZZ |
| 50 |
UblKg1bkwgZXQ7GB2tfk8LQPOTji8EWi36BNNjXpg5uYCMsmfGTdQNS3TlLjVLRN |
| 51 |
uQXiI7nfDxB9fwWRiNHrv+3Xxj0VKXpNRrT8qiEpUHSmiuurQ29DSPRDh7+dO3I6 |
| 52 |
4DpjoJRyNAbR915pdNy+TdwXhDr7gAPPXiamCHNzKYFcVe86HV335GEGTRHrK442 |
| 53 |
TTsjV/FwuvkFhR1ehU5Co7mrDxmTyDVKkbB6wFnA2lGIaQ/9Sw083AbUYH6uH8+M |
| 54 |
fcjwjczSAgjvrZzjXA78srdKomD/m+Bw0bUyNKc/dIRrDIiTvLZ3pwI/DCKaeM08 |
| 55 |
aM1KxG/B1XF6AUAsOzD98bEyq5LeXTrQSaXSEUwQc6VpLztrQsIMjMuQLOtwYRDI |
| 56 |
x8+/ZVsA+y3wKA8K28c9 |
| 57 |
=SWQu |
| 58 |
-----END PGP SIGNATURE----- |
Archives