Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > linux.debian.maint.python > #9544

Re: PAPT git migration

From Stefano Rivera <stefanor@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: PAPT git migration
Date 2017-06-01 06:10 +0200
Message-ID <tNpAR-62t-3@gated-at.bofh.it> (permalink)
References <tNh0B-4U-7@gated-at.bofh.it> <tNjvr-20L-1@gated-at.bofh.it> <tNk89-2vg-7@gated-at.bofh.it> <tNl4d-34b-5@gated-at.bofh.it> <tNoEO-5s8-15@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


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

Back to linux.debian.maint.python | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

PAPT git migration Stefano Rivera <stefanor@debian.org> - 2017-05-31 21:00 +0200
  Re: PAPT git migration "W. Martin Borgert" <debacle@debian.org> - 2017-05-31 23:00 +0200
    Re: PAPT git migration Stefano Rivera <stefanor@debian.org> - 2017-06-01 00:30 +0200
  Re: PAPT git migration Barry Warsaw <barry@debian.org> - 2017-05-31 23:40 +0200
    Re: PAPT git migration Stefano Rivera <stefanor@debian.org> - 2017-06-01 00:20 +0200
      Re: PAPT git migration Mattia Rizzolo <mattia@debian.org> - 2017-06-01 01:20 +0200
      Re: PAPT git migration Simon McVittie <smcv@debian.org> - 2017-06-01 01:20 +0200
        Re: PAPT git migration Scott Kitterman <debian@kitterman.com> - 2017-06-01 05:10 +0200
          Re: PAPT git migration Stefano Rivera <stefanor@debian.org> - 2017-06-01 06:10 +0200
        Re: PAPT git migration Brian May <brian@linuxpenguins.xyz> - 2017-06-01 07:10 +0200
        Re: PAPT git migration Brian May <brian@linuxpenguins.xyz> - 2017-06-01 07:10 +0200
          Re: PAPT git migration Simon McVittie <smcv@debian.org> - 2017-06-01 08:20 +0200
    Re: PAPT git migration Brian May <brian@linuxpenguins.xyz> - 2017-06-01 02:00 +0200
      Re: PAPT git migration Raphael Hertzog <hertzog@debian.org> - 2017-06-05 11:00 +0200
        Re: PAPT git migration Mattia Rizzolo <mattia@debian.org> - 2017-06-05 11:20 +0200
  Re: PAPT git migration Jordan Justen <jljusten@gmail.com> - 2017-07-10 03:00 +0200
  Re: PAPT git migration Daniel Stender <debian@danielstender.com> - 2017-08-01 00:40 +0200

csiph-web