On ven., 2016-07-22 at 13:36 -0400, Jeremy Bicha wrote: > > Let me know if it's still unclear or my instructions don't work.
It seems to work fine :) Thanks > > Because historically, we often end up releasing Git snapshots for > these themes, I didn't think it was useful to try to use gbp's > pristine-tar option. And as you can see from the README.source, my > workflow doesn't really use debian/watch. > > > I'm not completely sure but I think you should be able to have write access > > to > > the collab-maint area, where it'd be easier to “co”-maintain the packages, I > > think. > > Yes, I'm in the collab-maint team so I can push there. I just didn't > want to push such a major change without checking with the maintainer > first. I've merged the branch locally, and will push it when it's ok, so you should be able to start from there. Since the upgrade will drop greybird and blackbird, I think it'd be best to actually add a NEWS entry, on top of the changelog entry. But besides that, I guess it's fine. Regards, -- Yves-Alexis
signature.asc
Description: This is a digitally signed message part
