[pkg-otr-team] gbp vs. 1.0 source format
Holger Levsen
holger at layer-acht.org
Wed Feb 19 18:41:19 UTC 2014
Hi,
On Dienstag, 18. Februar 2014, intrigeri wrote:
> Cool. I've then done the same for libotr. Both pidgin-otr and libotr
> now live in Git, with a revamped packaging.
cool, so now it's just irssi-plugin-otr left. AFAIK it's debian packaging has
never been part of a git repo?!
> I would appreciate
> a review before I upload both, just to make sure we're on the same
> page.
I'm afraid I need to pass on this, at least for the coming days...
Just one thing: I noticed there is no README.Source - but then we dont want
this anyway, but rather document our workflow on
https://wiki.debian.org/Teams/OTR - correct?
> The only problem I've spotted today with source format 1.0 + applying
> patches directly in the packaging branch is that it makes it harder to
> track what changes have been forwarded and/or applied upstream, and
> which have not. To mitigate this a bit, I propose we try hard to
> immediately forward upstream any patch we have to apply (done that
> once today already).
turn it into policy instead, to only include patches which have been submitted
upstream to some tracker or which have been merged upstream?! IOW: do not
include patches which have not been sent upstream.
cheers,
Holger
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 828 bytes
Desc: This is a digitally signed message part.
URL: <http://lists.alioth.debian.org/pipermail/pkg-otr-team/attachments/20140219/8d513c73/attachment.sig>
More information about the Pkg-otr-team
mailing list