Path: csiph.com!feeder.erje.net!2.eu.feeder.erje.net!news.etla.org!aioe.org!news.servidellagleba.it!bofh.it!news.nic.it!robomod From: Stefano Rivera Newsgroups: linux.debian.maint.python Subject: Re: PAPT git migration Date: Thu, 01 Jun 2017 06:10:01 +0200 Message-ID: References: X-Original-To: debian-python@lists.debian.org X-Mailbox-Line: From debian-python-request@lists.debian.org Thu Jun 1 04:02:12 2017 Old-Return-Path: X-Amavis-Spam-Status: No, score=-6.879 tagged_above=-10000 required=5.3 tests=[BAYES_00=-2, FOURLA=0.1, HEADER_FROM_DIFFERENT_DOMAINS=0.001, LDO_WHITELIST=-5, MURPHY_DRUGS_REL8=0.02] autolearn=ham autolearn_force=no X-Policyd-Weight: using cached result; rate: -6.1 Mail-Followup-To: debian-python@lists.debian.org MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline X-Gpg-Public-Key: http://www.rivera.za.net/stefano.gpg User-Agent: Mutt/1.5.23 (2014-03-12) X-Mailing-List: archive/latest/14921 List-ID: List-URL: List-Archive: https://lists.debian.org/msgid-search/20170601040154.GD1153@bach.rivera.co.za Approved: robomod@news.nic.it Lines: 26 Organization: linux.* mail to news gateway Sender: robomod@news.nic.it X-Original-Date: Thu, 1 Jun 2017 06:01:54 +0200 X-Original-Message-ID: <20170601040154.GD1153@bach.rivera.co.za> X-Original-References: <20170531185815.GA1153@bach.rivera.co.za> <20170531173220.6df84975@subdivisions.wooz.org> <20170531221645.GB1153@bach.rivera.co.za> <20170531231639.jbfujevwijz2bu55@perpetual.pseudorandom.co.uk> Xref: csiph.com linux.debian.maint.python:9544 Hi Scott (2017.06.01_05:01:00_+0200) > As long as we have one team solution for this that is documented I > don't care what it is as long as it works. I don't think we should > have two approaches. Let's pick one and use it. Team members should > not be surprised when they look at a team git repo. I don't think anyone is advocating two approaches. But we don't need to enforce the use of pq. We have git repos that are compatible with the use of pq, and you can use it to manage your quilt series, if you wish. The serialized quilt series is what we have in the shared git repo. The upside of not doing a once-off migration to pq-friendly patch metadata is that the git migration will cause less churn on source packages. That patch metadata churn can be delayed until the next upstream release is imported. The downside is that it's up to the maintainer to notice and re-format their patch metadata, the first time they want to use pq, after the migration. SR -- Stefano Rivera http://tumbleweed.org.za/ +1 415 683 3272