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


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

Re: so you want to migrate DPMT/PAPT to git? look at what pgk-perl did!

From Simon McVittie <smcv@debian.org>
Newsgroups linux.debian.maint.python
Subject Re: so you want to migrate DPMT/PAPT to git? look at what pgk-perl did!
Date 2015-08-07 13:30 +0200
Message-ID <pUO0y-6r7-21@gated-at.bofh.it> (permalink)
References <pUqUi-6vT-7@gated-at.bofh.it> <pUCC6-6KD-9@gated-at.bofh.it> <pUNea-5gC-17@gated-at.bofh.it>
Organization linux.* mail to news gateway

Show all headers | View raw


On 07/08/15 11:30, Sandro Tosi wrote:
> On Fri, Aug 7, 2015 at 12:18 AM, Barry Warsaw <barry@debian.org> wrote:
>> But, is that a good thing?  quilt itself is a PITA to use IMHO
> 
> a lot of people seems to appreciate quilt (I know that 3.0 (quilt)
> doesnt necessarily reflect in using quilt). It's not perfect but I
> find it usable and in line with the style of other packaging tools.

I agree with Sandro about repository contents while disagreeing about
the quilt(1) command-line tool, which is perhaps an interesting perspective.

I avoid quilt(1) wherever possible, and whenever I use it to resolve
some weird patch-queue corner case, I have to look up how it works.
However, the patch-queue format, and patches-unapplied git repository
contents, make a lot of sense to me: the git history contains exactly
the parts that don't get rebased.

To avoid quilt(1), I use "gbp pq" instead. What I commit to git as a
result interoperates with quilt(1), in the sense that someone like
Sandro could clone one of my repositories, manipulate the patch queue
with quilt(1), and not have to know or care that I used gbp pq; and I
could work with one of Sandro's repositories with gbp pq, without having
to deal with quilt. That seems like a nice property to have.

(Example repositories: dbus, ioquake3)

    S


-- 
To UNSUBSCRIBE, email to debian-python-REQUEST@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
Archive: https://lists.debian.org/55C495BB.4010501@debian.org

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


Thread

so you want to migrate DPMT/PAPT to git? look at what pgk-perl did! Sandro Tosi <morph@debian.org> - 2015-08-06 12:50 +0200
  Re: so you want to migrate DPMT/PAPT to git? look at what pgk-perl  did! Barry Warsaw <barry@debian.org> - 2015-08-07 01:20 +0200
    Re: so you want to migrate DPMT/PAPT to git? look at what pgk-perl did! Sandro Tosi <morph@debian.org> - 2015-08-07 12:40 +0200
      Re: so you want to migrate DPMT/PAPT to git? look at what pgk-perl  did! Simon McVittie <smcv@debian.org> - 2015-08-07 13:30 +0200
        Re: so you want to migrate DPMT/PAPT to git? look at what pgk-perl  did! Barry Warsaw <barry@debian.org> - 2015-08-07 16:50 +0200
      Re: so you want to migrate DPMT/PAPT to git? look at what pgk-perl did! Scott Kitterman <debian@kitterman.com> - 2015-08-07 15:20 +0200
        Re: so you want to migrate DPMT/PAPT to git? look at what pgk-perl did! Sandro Tosi <morph@debian.org> - 2015-08-07 15:40 +0200
          Re: so you want to migrate DPMT/PAPT to git? look at what pgk-perl  did! Barry Warsaw <barry@debian.org> - 2015-08-07 16:30 +0200
          Re: so you want to migrate DPMT/PAPT to git? look at what pgk-perl did! Scott Kitterman <debian@kitterman.com> - 2015-08-07 19:00 +0200
            Re: so you want to migrate DPMT/PAPT to git? look at what pgk-perl did! Vincent Bernat <bernat@debian.org> - 2015-08-15 20:30 +0200
              Re: so you want to migrate DPMT/PAPT to git? look at what pgk-perl  did! Barry Warsaw <barry@debian.org> - 2015-08-17 17:20 +0200
                Re: so you want to migrate DPMT/PAPT to git? look at what pgk-perl  did! Steve Langasek <vorlon@debian.org> - 2015-08-17 18:00 +0200
      Re: so you want to migrate DPMT/PAPT to git? look at what pgk-perl  did! Barry Warsaw <barry@debian.org> - 2015-08-07 16:10 +0200

csiph-web