On Fri, Apr 28 2017, Yves-Alexis Perez wrote: > On Sun, 2017-04-23 at 15:34 -0700, Gerald Turner wrote: >> Let me know if it would be at all helpful to run a publicly >> accessible git repository (pull request rather than patches), I've >> been using gitolite3 with private SSH access, but attaching some >> read-only HTTPS front-end has been on my TODO list forever. > > Thanks for your patch serie but actually I already did this not that > long ago, I just didn't push the work yet.
Great! This shall be interesting - rebasing my private gbp repo with
your changes at alioth - looking forward to learning new git workflow
;-)
Among the flurry of BTS mail I triggered last Sunday, did you happen to
catch my offers to:
1. Work on debian/copyright until it's near-perfect (I'm confident the
work on I did on 5.5.1->5.5.2 delta is correct, but while working
on that I noticed inconsistencies since older releases, which I
mostly ignored). I had done something similar with hostapd/
wpa_supplicant a few years ago with guidance from Stefan
Lippers-Hollmann.
2. Create separate packages per plugin (with extra attention paid to
Depends, Recommends, Suggests fields), at a minimum create separate
attr-sql/sqlite/mysql plugin packages (bug #718302), or maximally
create a separate package for every plugin, or something in
between. Ultimately enabling additional plugins that myself and
several other users have been requesting.
BTW, the BTS seems to have dropped PATCH 01/12, not that this matters
anymore, but I'm curious about what the limitations BTS has on message
size, etc. (it was the giant 'gbp import-orig' patch).
--
Gerald Turner <gtur...@unzane.com> Encrypted mail preferred!
OpenPGP: 4096R / CA89 B27A 30FA 66C5 1B80 3858 EC94 2276 FDB8 716D
signature.asc
Description: PGP signature
